Hi @koksime-yap_5909 , This is a known issue and will be fixed via PG-3063 in teh next maintenance release, shipping later today. Thanks, Steve

Hi @koksime-yap_5909 , That's just a "suggestion box" in the UI - you can just type in whatever you'd like. But in general you shouldn't upload files via the UI, but using maven. Thanks, Steve

Hi @koksime-yap_5909, No; when you use LDAP, then you need to manage the LDAP users' groups in your directory. Here is a recent discussion on the topic: https://forums.inedo.com/topic/5471/feature-suggestion-allow-ad-users-to-be-added-to-built-in-groups Thanks, Steve

Hi @patrick-tessier_4584 FYI, dotnet nuget and nuget.exe are effectively the same thing - they both invoke the NuGet CL.. The nuget.exe is a standalone version of the CLI and dotnet nuget is part of the .NET SDK. The issue is that your copy of nuget.exe was ancient and didn't work. Cheers, Steve

Hi @kc_2466 , Thanks for the report; we'll get this fixed in the next maintenance release (this week) via PG-3064 Thanks, Steve

Hi @misael-esperanzate_5668 , That makes perfect sense; when package caching is enabled, the package files are added to the feed and stored on disk. When it's not enabled, they are simply streamed from the server. Something is interfering with your disk storage that is deleting (quarantining) files on disk. You will need to follow the troubleshooting I identified above - it's probably a security tool. Suggest using AWS Lightsail to get a test box in an environment you can control. Thanks, Steve

@dean-houston Thanks Dean, looks like it worked. I guess I am still a new user too!

Hi @misael-esperanzate_5668 , Although ProGet can handle invalid version numbers for Maven packages, this one is a extra invalid version number (it starts with a "v") and unfortunately we can't support them at this time. ProGet requires that packages follow the ~20 year Maven standard that "packages start with a letter and versions start with a number". Sadly this team didn't like those standards and opted to do their own thing. The issue comes with identifying whether com/google/apis/google-api-services-healthcare/v1-rev20240731-2.0.0 is an artifact or a version. Because ProGet is not a basic file server, things like package names and versions matter. Anyway this will require a significant and risky change to the API so we won't consider it at least for another major release. -- Dean

Hi Marc, I'm not sure what you mean by 2024.8-r1 but the -ci.x and -rc.x images are prerelease versions. Sometimes they are the same as the release versions, sometimes they aren't. I wouldn't use prerelease versions unless we suggest them to you for a specific issue you're facing. -- Dean

@tames_0545 thanks for letting us know! We'll see if we can improve troubleshooting on this in the future as well!

Hi @darren-sloper_5044 , ProGet does not currently produce HTTP Access Logs, though we are considering that for a future release. It's really easy to add it via an IIS reverse proxy (WIndows) or with some NGNIX settings if you're on Linux Dean.

Hi @carsten_1879, Thanks for trying it out. It is new, and has not been tested as much against older repositories. That said, we've reproduced this error and it's now fixed in the latest build - buildmaster:25.0.0-ci.28 if you would like to try it again. It's caused by older repos that don't support offset deltas being transmitted during a clone or fetch. Small repos that we used for testing ADOS so far were not large enough to have deltas at all, so those worked. So far as I can tell, the repository name containing a dot doesn't have any effect. Thanks! -Greg

Hi @kc_2466 , Understood, that was the same reason given before. Our products' AD/LDAP integration works different than JIRA/TeamCity (live lookup vs sync) so it's just not that simple. We're not willing to add complexity to work-around "dumb" organizational policies -- what you described is the whole point of AD/LDAP (centrally administered access). It's possible to delegate group administration in AD, but if they don't want to do that... I guess they are okay with you just creating less-secure built-in users until they get around to completing their tickets ;) Thanks, Alana

Hi @thomas_3037 , ProGet does not support these, as they are not "real" Debian repositories: These are used only by the Debian installer and are not installed on a Debian system under normal circumstances. Unlikely we would add support for them, given the highly-limited use case. Thanks, Alana

Hi Alana, Thank you very much for your quick response and fix! Cheers, Michael

Hi @kc_2466 , nice catch! We'll get it fixed via PG-3060 in the next maintenance release!

The same exact scenario is bothering us as well. Any improvements in this case will be very helpful. We're deleting the sqlite files every 4 hours to be able to make it work most of the time, but a better permanent solution would be nice.

@stevedennis I tried in a docker image but also could not reproduce it reading SBOM from the UI. We have a major release ahead perhaps i can try after the release, but failing builds scares people me included.

Hi @caterina , I agree and there doesn't seem to be any good usecases or official guidance from npm tags command, but we do not recommend using them: https://blog.inedo.com/npm/smarter-npm-versioning-with-semver/ From the api/technical standpoint, npm tags are a little weird -- a package themselves doesn't contain tags. Instead, the registry has a key/value tag store. By convention, the store has keys like latest and values like 4.8.1, but it seems to allow anything? At least from data we've seen on npmjs.org In any case, the npm client seems to set a latest tag, so we'll just support that use case then. FYI here is the logic/code I added: var tags = await this.GetPackageTagsAsync(purl.Name, false, cancellationToken: cancellationToken); if (tags.TryGetValue("latest", out var latestVersion) && latestVersion == PackageVersion<SemanticVersion2>.Parse(purl.Version)) await DB.Npm_SetTagVersionAsync(toFeed.FeedId, purl.Name.Id, "latest", purl.Version, DateTime.UtcNow); It sets the latest tag on the other feed if the current feed's latest tag points to the package you are promoting. Thanks, Alana

@carl-westman_8110 I was wondering whether you'd be willing to share your Bicep script or could give some tips from it? I'm looking to set up pretty much exactly what you have: Azure Container App / Azure SQL DB / Azure Storage and would very much appreciate seeing how you did it without having to reverse-engineer everything. Thanks for a short answer, even if you can't share.