Welcome to the Inedo Forums! Check out the Forums Guide for help getting started.

If you are experiencing any issues with the forum software, please visit the Contact Form on our website and let us know!

  • proget 2023 - iis vs internal web

    3
    0 Votes
    3 Posts
    8 Views
    U
    Hi Alana, thank you very much. will do.
  • 0 Votes
    8 Posts
    22 Views
    P
    @atripp Thanks for the fast reply and the bypass. Best regards PhilippeC.
  • Sync BM from OT

    otter buildmaster
    9
    0 Votes
    9 Posts
    24 Views
    atrippA
    Hi @philippe-camelio_3885 , We haven't investigated or changed this code in very many years (especially within the last year), so I wouldn't expect a changed result. Can you try the same troubleshooting steps as above? To find out where the invalid JSON is? Maybe it's comma again? FYI - we use Newtonsoft.Json for both serializing and deserializing (as you can see from error). It's really odd to be generating invalid JSON, but that's what the message is It could be related to an obscure bug, etc. We just have no idea and haven't investigated in past year. Thanks, Alana
  • Unable to upload Debian Package.

    Locked
    15
    0 Votes
    15 Posts
    57 Views
    atrippA
    @frei_zs I'm also replied to your ticket (EDO-10276), but wanted to reply here as well. I'm going to lock this thread after, since it's a different issue. Unfortunately "tar" files are more of a convention than a standard, and not all libraries can read files created with different libraries. We are using one of the most "forgiving" tar libraries (we use four different ones!) in this particular scenario, but maybe aptly conventions aren't forgiving enough? FYI - here is what we're doing with the library public byte[] ReadControlBytes() { using var control = TarReader.Open(this.Control); while (control.MoveToNextEntry()) { if (control.Entry.Key == "./control") { var bytes = new byte[control.Entry.Size]; using var entry = control.OpenEntryStream(); ReadBlock(entry, bytes); return bytes; } } throw new InvalidPackageException("Package does not have a control file."); } We will need to inspect the file and see if we can determine what's wrong, and if it's an easy fix, we'll do it.
  • 0 Votes
    7 Posts
    26 Views
    atrippA
    @hashim-abu-gellban_3562 nice find, correct that was a typo :)
  • Unable to add license to package

    4
    0 Votes
    4 Posts
    17 Views
    atrippA
    Hi @v-makkenze_6348, It's hard to say for sure, but there's clearly some kind of database timeout problem here when running Projects_GetReleaseAnalyzerData . I suppose you could try running that directly, and see if it takes a long time? I suspect the issue is that you have too many active releases. This is a major issue with ProGet 2023's feature -- it was designed with the assumption that users would archive releases, but we've seen thousands in the field. If you have a lot of active releases, this cause some big performance issues. ProGet 2024 auto-archives builds (the new word for releases). Cheers, Alana
  • Proget Python connector to PyTorch Cuda Index

    proget python connectors pypi
    4
    0 Votes
    4 Posts
    11 Views
    atrippA
    Good news @m-karing_2439 , This works in ProGet 2024! More specifically, when rewriting/refactoring the PyPi feed, we added support for this "unconventional" repository - specifically, one that doesn't follow the /simple convention or use any of the JSON/warehouse api. Cheers, Alana
  • Apply License via API

    2
    0 Votes
    2 Posts
    10 Views
    atrippA
    @forbzie22_0253 you can use the same ProGet Free on multiple instances
  • ProGet Enteprise License Update

    2
    0 Votes
    2 Posts
    6 Views
    atrippA
    Hi @scott-wright_8356 , You can ignore that message; not sure how/why it occurred, but the consequence is that the message that the license key was updated wasn't immediately dispatched to the other nodes due to some timint issue. So that means it could take a few minutes for the other nodes to reflect the new license key. We should probably just ignore that error. let us know if you keep seeing "No primary service node has been registered." and we can investigate further. Best, Alana
  • VulnerabilityDownloader fails with error

    8
    0 Votes
    8 Posts
    24 Views
    J
    Looks like success! [image: 1711638528204-cde07fce-746b-406f-8e31-186207661cc6-image.png] Thanks for addressing this so quickly.
  • Timeout in build when running pgscan

    8
    0 Votes
    8 Posts
    24 Views
    ValentijnV
    Hi, I checked again and the number of packages is correct when the build succeeds. Had to run the build 9 times before I had a build that did not give a timeout. Before i counted the number of components in the SBOM but the app itself is also a component and i have two SBOM's so therefore i was missing two packages. I get the feeling that during the failing builds the SBOM is uploaded but not completely processed. So the next build its processed and thats when i see three SBOM's or four if the build succeeds. Still no clue why this is the only build that has these failures, its not our biggest or most complex product. We don't have many builds that contain both npm and nuget packages but there are others. All builds are run at least once a week so the others with two pgscans are ok.
  • Lots of Powershell and Conhost processes

    2
    1
    0 Votes
    2 Posts
    9 Views
    atrippA
    Hi @Justinvolved , This is not uncommon with PowerShell; in general the processes will be closed, but there are enough scenarios with long-running/hanging PowerShell scripts where those processes will report termination but the process will not be terminated. So they can stick around I'd recommend using the Inedo Agent instead, even if it's on the same sever. That gives better process isolation compared to the local agent, and you shouldn't see this behavior for too long. The local agent runs in-process. Cheers, Alana
  • npm install slow on proxy feed

    3
    0 Votes
    3 Posts
    26 Views
    A
    Hi Dean, we noticed that when performing an "npm install" against ProGet it will successively open ~1000 sessions. We tried a couple of values for Web.ConcurrentRequestLimit under "Administration --> Advanced Setting" (20, 50, 100, 200) and found out, that when using 100 we get the same (or even better) performance for an "npm install" compared to registry.npmjs.org. We're not exactly sure how Web.ConcurrentRequestLimit works but we assume that it has some relation to the default pool size for the SQL Server connection used by ProGet, which also seems to be 100. I just wanted to let you know, that by setting Web.ConcurrentRequestLimit to 100 the performance of "npm install" is back to normal. Best, Andreas
  • Database Error

    6
    0 Votes
    6 Posts
    39 Views
    atrippA
    FYI - we plan to fix this in ProGet 2023.32 via PG-2613
  • Maven Andriod Endpoint URL

    7
    0 Votes
    7 Posts
    21 Views
    atrippA
    Hi @scott-wright_8356, I looked into this further; for Maven feeds, the Connector Health Check simply queries the downloaded index. If there is no downloaded index, then it reports back as healthy. If there's an error with the index, it reports an error. However, most maven repositories don't have a downloadable index. Anyway the health check is not very useful, and we plan to revisit the functionality in the future, since there's really no way to determine if ProGet can download an artifact unless you know the exact name. Thanks, Alana
  • SQL Server execution timeouts after updating to 2023.31 (Build 5)

    7
    1
    0 Votes
    7 Posts
    41 Views
    atrippA
    @appplat_4310 thanks for the update! We also applied the patch to the next maintenance release, so you shouldn't have any issues going forward then!
  • ProGet dropPath for package imports

    6
    0 Votes
    6 Posts
    19 Views
    F
    @atripp thanks for confirming.
  • Maven feed for cache

    8
    1
    0 Votes
    8 Posts
    15 Views
    atrippA
    Hi @scott-wright_8356 , Thanks; it sounds like the underlying issue is indeed Google Android connector you added. I don't have an information or idea on why that might be the case... some third-party repos (Maven, PyPi, NuGet, etc.) are just really slow and buggy. ProGet is basically acting like a proxy server here, so "garbage in, garbage out" applies - if the connector is slow and error-prone, then you will experience slowness and errors. Sometimes third-party repos will create packages that don't follow the specifications but just happen to work in certain versions of clients. That could be what's happening here. In cases like that, we can really only address those on a case-by-case basis, and we'd need to know exactly how to reproduce the error and investigate it later. Best, Alana
  • Proget: Documentation of 2024 Projects Preview feature

    4
    0 Votes
    4 Posts
    17 Views
    rhessingerR
    Hi @sebastian, That option can be ignored. We have decided to remove that option from the feature because it was only something that changed a UI color and had no real affect on the operation. It looks like we missed it in that UI. We will remove that in an upcoming release of ProGet. Thanks, Rich
  • This topic is deleted!

    1
    0 Votes
    1 Posts
    7 Views
    No one has replied
Inedo Website HomeSupport HomeCode of ConductForums GuideDocumentation