Topics created by brett.polivka

Digging more into this, it appears that "pip search" is basically unsupported at this point, even by pypi.org. You can disregard this issue.

Hi @brett-polivka, We've published v2.0.1 of the Azure extension for ProGet, which should resolve this issue. You can install it from the Admin->Extensions page. Let us know if you are still having the issue after updating the extension. Thank you! -Greg

Hi @brett-polivka, No problem! We are expecting this fix to be released on Friday. We will let you know if anything changes! Thanks, Dan

Hi @brett-polivka, I haven't tried ghcr, but in my experience GitHub is really unstable on the API/integration side when it's outside of their core source/Git hosting functions (e.g. Packages are notoriously buggy), so if your PAT is okay, then this is the most likely scenario. The Connector Health Check for Docker uses the catalog API (/v2/_catalog), and the response should look something like this: https://proget.inedo.com/v2/_catalog. This endpoint is particularly buggy in other repositories (especially ones that require authentication/authorization), so my guess is GitHub introduced a regression or something on their implementation. Another possibility... 403 is access related, so it could be something on your proxy side; please also check your Proxy settings, or something on your network side.

Hi @fabrice-mejean_6049 , @brett-polivka Thanks for the feedback! With ProGet 2023 out of the way (which made developing new feeds a lot simpler), and the addition of the Cargo Registry Web API, this is something we're much more open to implementing. We want a user partner, someone who is already using Rust/Cargo and would be able to work with testing/developing this for us. Currently there hasn't been any market demand from prospects or other users.... and for your team, seems like a "nice to have" more than anything. Thanks, Steve

@brett-polivka sorry about that, there's always room to improve the testing, and you just got "unlucky" with a few edge cases that slipped through the cracks. But not to worry -- you can just downgrade the extension by following the manual installation instructions - the 1.9.0 of Azure will still use the old libraries - https://proget.inedo.com/feeds/Extensions/inedox/Azure/1.9.0

Looks good! I had to create a volume mount for /var/proget/extensions to get the extension upgrade to persist, but it seems to fix the problem. Thanks!

I also confirm I didn't get any more timeouts on the latest version. Very good!