Hi @richard-carpenter_9650 , Thanks for confirming that; that is really strange. I just tried it msyefl and got the same result. The technical answer is that PowerShell gallery is sorting the feed alphabetically, and is only returning the top 100 entries. Of those entries, all but two are unlisted. So that's all you see. Not a great UX, so hopefully it goes away (i.e. they return the default sort order by downloads), or maybe we can sort differently ourselves. We're not too keen to change this, since it's the "very sensitive" legacy NuGet v2 API, but perhaps in v2023 we can alter this. Cheers, Steve

Hi @martin-noack_4528 , Nice points :) We added this to our ProGet 2023 roadmap as a "Nice to Have"; we're a little behind on the release now so I don't know if it will make it, but we will reevaluate after 2023.0 is released at that point. Cheers, Alana

Hi @js-enthoven_2797, Unfortunately I'm not very familiar with debugging apt :( The only one I was familiar with was the InRelease-related error, which you worked around. Otherwise, I haven't seen these before, but they seem to be warnings, so maybe it's okay and is working? It does say "All packages are up to date". I don't really know what they mean, or if it's related to ProGet, apt configuration, or the package I searched for the text of these errors ("No Hash entry in Release file"), and there are a lot of suggestions on what to do... they are all different, and I have no idea what might work. The "Connection timed out" is really strange too. Maybe it's related to proxy, or something? A blank page is to be expected if you have no packages in that scope; otherwise you will see a number of "Paragraphs", one for each package. Cheers, Alana

Hi @v-makkenze_6348, When you enable the preview feature for ProGet Vulnerability Central, ProGet will add a vulnerability source name PGVC automatically, but it will not show under the vulnerability sources. It looks like after you enabled that, you added a new ProGet Vulnerability Center (which will default the name to "ProGet Vulnerability Central"). So the ProGet Vulnerability Center source should be left off and can probably be removed. That is definitely what was causing a duplicate vulnerability. Thanks, Dan

Hi @atripp. Yes, that worked. Thank you for all the help. -marc

Hi @kichikawa_2913 , PG-2290 was the regression fix, and it was included in ProGet 2022.22 Cheers, Alana

Ok, no prob! Thank you!

Hi @philipp-cender_3322 , Looks like you're making good progress :) I ran the command .\inedoagentservice.exe run but the command only stated that it does: "Starting agent connector to the otter-host-fqdn on port 8630" That's okay to see; it means that its working as expected. I there was an error, you would see it. But for Source 10.67.0.17 something like a token exception is stated In the screenshot, it seems okay and doesn't report an error. So I think it's okay? The exception message is some kind of OS-level error, and I'm not sure what it means exactly. But it's a SSL/TLS issue. In this case, if you search for the text of the error ("Die Anmeldeinformationen, die dem Paket übergeben wurden, wurden nicht erkannt" -- but perhaps English is better), you can probably get some details on how to fix it. It could be some obscure operating system configuration. If i open otter at Port 8630 (Agent Listener) on Firefox webbrowser i get something like that: PR_CONNECT_RESET_ERROR It's not possible to "browse" such a connection; the Inedo Agent uses a proprietary, TCP-based binary protocol. So you will always get errors if you try to browse, telnet, etc. Cheers, Alana

Hi @Justinvolved , That error message is coming from here: https://github.com/Inedo/inedox-git/blob/master/Git/Git.InedoExtension/Operations/CanonicalGitOperation.cs#L73 Basically, it means that value you've specified for From is not a known Secure Resource. It's not a common error, and is likely the result of deleting/re-adding something. I would remove the From argument from your OtterScript altogether (just leave it as Git::Checkout-Code;). I don't think you need it. Your build should already associated with a repository, branch, and commit. Cheers, Alana

Hi @hashim-abu-gellban_3562, Happy to hear the config fixed your issue on the clair container. In ProGet v2022 we moved the feed vulnerability source to the Reporting & SCA > Vulnerabilities > Configure Vulnerability Download Blocking page. You should be able to wire it up from there. I'll make sure to update our documentation with these changes as well. Thanks, Rich

@e-rotteveel_1850 thanks for explaining that, that's great to know! Sometimes it's almost impossible to learn how these feed/package types are actually used, especially since we don't develop in those languages and really just focus mostly on API reverse-engineering ;) FYI We are targeting late April for 2023.0 release

Hi @jim-borden_4965 ! I think that the "delete old versions" option of Retention Rules might be what you're looking for; that will let you keep the last "X" versions of each package. That, in combination with "unused versions" (i.e. not recently downloaded) typically cover nearly all desired retentions. As far as a "feed independent" API, that's on our list as a "nice to have", and I don't know how much of an API we'll get in the first version of ProGet 2023. The "hard part" is usually specifications/docs, so if you have any ideas we'd be very open! Currently, our idea is base it off of the upack api: https://docs.inedo.com/docs/upack-feed-api-endpoints Some things will be more difficult (or impossible?) than others. Especially for multi-platform package types like ruby, python. But TBD. Cheers, Alana

Great thank you!

Hello @atripp Thanks for sharing the code segment. I believe that the issue could be somewhere else and not related to Proget at this point. I attempted to push to Amazon ECR using the same nerdcrl and found that I'm able to push it just fine. This leads me to believe the problem is not with nerdctl or docker cli for that matter. I came across this thread which I feel does not serve as a proper documentation (but relatable though). Bottomline, I wouldn't want to break anything that is working fine. I'm going to deploy Proget on AWS Lightsail and compare with what's going on the k8s deployment. Btw, I upgraded my Proget to 22.0.26 and the result was the same.

Hi @e-rotteveel_1850 , sorry I missed the notification on this b/c of how I categorized this. Yes.. Q2 (late April for now) is the current plan, though this is something we would likely do after the main release.

Hi @falk-winkler_2111 , I believe in this case, you'll just enter the access token as the password, and select "Bearer" as the authentication type. Cheers, Alana

I now changed to 2022.25, and CURL uploads are working again. Thanks!

@ade8s_7742 so glad to hear that! It's really rare, but glad it wasn't database corruption!!

Hi @darturow_6059 , I think the equivalent to a "Generic Repository" would be ProGet's asset directory: https://docs.inedo.com/docs/what-is-an-asset-directory However, there is no "connector" possible, except to another ProGet asset directory. Cheers, Alana