Hi @maciej-luszczynski_5271, Thanks for bringing this to our attention. I have corrected the example as suggested. Thanks, Dan

@atripp the health endpoint looks good, thanks

@francesco-campanella_3733 thanks for continuing to research this - we just haven't had a chance to look further. Did you try editing the feed settings (especially the Feed Features, which would save a new Feed Config), and then re-saving again? We will fix the bug, I would just like to be able to reproduce it so we know for sure what's causing it :)

@atripp thanks, resolved now.

Hi @sebastian, Thanks for sharing your thoughts on this! Few things to point out... [1] The "Missing Package Problem" is not as bad in ProGet 2024, mostly because it will only apply when there's a license rule. In ProGet 2023, a "missing package" would happen even for vulnerabilities. [2] We're working on a new feature/module (tentatively called "Remote Metadata") that is intended to routinely cache/update meatdata from public repos like nuget.org, npmjs.org, etc. This feature enables two usecases: Routinely update "server-side metadata" like Deprecated, Unlisted on cached packages Fetch metadata for packages not in ProGet during build analysis It works somewhat independently, and basically it'll just show up on the Admin tabs as like "Remote Metadata" and you can configure providers, urls, etc. I hope to have a prototype in a couple weeks and will post some details on a new forum posts. As an FYI this is something we will limit in the Free/Basic editions and have full-featured in the ProGet Enterprise product. [3] "Package In ProGet" could be a policy rule to add after RMetadata feature, though it's probably not a big deal if ProGet can detect licenses thanks to RMetadata Best, Alex

Hi @sebastian, I took a quick look, but its not a simple cherry-pick; this is a bug in the code that does policy analysis, and there were enough changes between ProGet 2023 and ProGet 2024 in that to make it a bit risky / time-consuming to bring over... Thanks, Alana

Just wanted to give a brief update to the issue from @mortenf_3736 that we discussed via the support ticket. We were never able to get to the bottom of it, but it was entirely related to running on ACA. Container Setup VM Setup Azure Container Apps - Running 4 minimum replicas, max 8 replicas, each 3 cores and 6gb memory Two D4 (4 cores, 16GB memory) VM with internal load balancer in front between them Mapped storage from Azure Storage Account v2 Fileshare Managed Premium Shared Disk, connected to Fail-over Cluster and shared between both VM Azure SQL Database with 4 cores dedicated Azure SQL Database Server less, scaling between 0.5 to 4 cores This doesn't seem to be related to Linux/Docker/Kubernetes, as we have several high-traffic users on Kubernetes clusters without issues like this. However, we have seen a handful of Azure-related problems over the years that manifested in ProGet: a bad hard drive that was constantly corrupting packages another had really slow disk I/O (one server out of a handful) we've seen a buggy storage driver cause some big impacts across some kind of storage configuration So we believe the issue is the Azure platform itself, similar to the above hardware/software glitches we've uncovered over the past. We're doing our best to research/identifying issues, and Inedo/ProGet Users aren't the only ones who are experiencing pain like this. Consider this report from a Azure "big data" user: I have suffered from chronic socket exceptions in multiple Azure platforms - just as everyone else is describing. The main pattern I've noticed is that they happen within Microsoft's proprietary VNET components (private endpoints). They are particularly severe in multi-tenant environments where several customers can be hosted on the same hardware (or even in containers within the same VM. The problems are related to bugs in Microsofts software-defined-networking components (SDN proxies like "private endpoints" or "managed private endpoints"). I will typically experience these SDN bugs in a large "wave" that impacts me for an hour and then goes away. The problems have been trending for the worse over the past year, and I've opened many tickets (Power BI, ADF, and Synapse Spark). Other Azure users (who are much more technical than we are) have confirmed that there are indeed severe issues with their SDN infrastructure. Microsoft does appear to be aware of these endemic issues with their platform, and for the time being we simply cannot recommend using Azure's container services for anything that will have any kind of load. Hope that gives some insight in case anyone stumbles across this thread. Alana

Thanks, we're planning to upgrade tomorrow. Will keep you updated.

Hi @arkady-karasin_6391, I'm afraid we don't have enough information to troubleshoot the problem. The use case you describe (using ProGet as an offline cache) is very common, so it might be some kind of misconfiguration on the npm side or something. I don't realy know. I would check the npm logs, try to monitor http traffic, etc. If you can "see" the package in ProGet as a Remote Package, and then download the package from the web page, then the npm client can do the same. The npm API cannot "see" whether it's a local, cached, or remote package, so the package is pulled regardless. Best, Alana

@atripp thanks for confirming

@Alex_9348 found them! https://s3.amazonaws.com/cdn.inedo.com/release/rules.pdf Enjoy :)

@atripp Ohh, sorry my mistake, changed it to proget, same problem actually. Will check at our end.

@atripp Thanks

@stevedennis I swtiched from "V3: Active Directory (LDAP)" to "V4: Active Directory/LDAP (Preview)" and all is good now. Logon went from two/three minutes down to one second.

Hi @Darren-Gipson_6156, No problem! Glad it is working. ProGet 2024.6 will include a fix for this issue, PG-2695. So hopefully this won't happen again! Thanks, Rich

I have done more digging and you are right. My windows service wasn't actually pointing to the exe that was updated If i run the updated service, funnily enough it works!

In that case please just upgrade and it should be resolved :)

Hi @rick-kramer_9238, You could do this via the API; it would involve first Querying Package Versions, and then for each version returned, Setting Package Status. I think it'd be a "relatively easy" script to write - so if you create one that can do it, please share :) Hope that helps, Alana

Hi @forbzie22_0253 , This refers to Delete Package, which was introduced in ProGet 2023: https://docs.inedo.com/docs/proget-api-packages-delete We don't really document/track what Native APIs change between releases, so I'm not really sure: https://docs.inedo.com/docs/proget-api-http#native-api-endpoints You can do a comparison in the /api/reference page. Thanks, Alana

@atripp I thought the fix was for Otter !