I added this to our Otter 2023 list of items to review/consider :) Please stay tuned

Hi @en_1446 , Not sure what version of ProGet you're using, but this seems to be on the recent versions I've seen, so I would recommend to upgrade :) Cheers, Alana

@atripp said in BM - Help needed for Git checkout: shexec echo hello world; I have no issue to run a shexec. This is just the git-checkout. The server is also configured thru Otter without any problems ... I am using artifact captured from localhost so it is OK for me I will make other tests later

Hi @kichikawa_2913, You can ignore the Age field; it's just used internally by Visual Studio, along with the Id. Not sure why, but it's a strange value in PortablePDB files. Here's more on what Age means if you're dying to read PE-COFF specifications https://github.com/dotnet/corefx/blob/master/src/System.Reflection.Metadata/specs/PE-COFF.md#codeview-debug-directory-entry-type-2 Best, Alana

Thanks, I updated and feed cleanup is back to seconds instead of hours [image: 1692943179937-5b6aebe8-48a0-410b-bc47-c5d54f86e8f6-image.png]

@apxltd I'll wait for v2024

Hi @atripp Oups, After your reply, I checked the ssh config on the target server and I forgot I allowed ssh root connection only from the Otter / BM server. Match Address XXX.XXX.XXX.XXX PermitRootLogin prohibit-password Changing the address solved the error My bad Thank you for your time

Hi @ccordova_8628 , ProGet requires SQL Server; Postgre/MySQl are not supported. Cheers, Steve

Hi @ivan-magdolen_6846, It looks like you're on the right track with finding the XML for that key. Since you're automating the installation, and already have DBO access to the ProGet database, I would suggest just directly adding it to the database using that stored procedure. You can also add/edit some values (like license key) if you want to the Configuration table. Alternatively I guess you could try Admin:Admin as the API key, since that account will be created by default. I'm not sure if it will work with the native API however. Best, Alana

Thanks Steve, That was helpful! Regards, Priyanka

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

Thanks! Merged and released.

@atripp Thanks for your reply , following your instructions, the problem has been resolved in vs2022 , cmd like this: dotnet nuget add source https://someServer/myTeam -n myTeam -u myUsername -p myPassword --store-password-in-clear-text And, another way to solve (tested in VS2017 and VS2022) can add a nuget.config in solution root directory: <configuration> <packageSources> <add key="mynuget" value="my source url" protocolVersion="3"/> </packageSources> <packageSourceCredentials> <mynuget> <add key="Username" value="myuser" /> <add key="ClearTextPassword" value="mypwd" /> </mynuget> </packageSourceCredentials> </configuration> So kind of you,thanks again.

Hi @w-repinski_1472, We currently do not have any mechanism for alerting the user when an extension update is available. Our guidance around this is to check extensions for updates after a product is upgraded or when instructed by support. In this case, it was my fault for not alerting you to upgrade the extension to fix this issue. I'm sorry for that and I will make sure this does not happen again. Also, many extensions are included in the install package. These extensions are updated automatically when the product is upgraded. So this won't be a problem with most extensions, it just so happens that the clair extension is not an included one. Please let me know if you have any other questions for us. Thanks, Rich

@stevedennis said in Proget Service/Site Crashes with 500 Error: shared memory provider error 40 Thank you for the insights, I was also thinking the sql server was the most significant thing. It is on the same server but it's also a virtual server, I don't think it's a hardware failure there. There is another sql server running on the server for chocolatey central management, there may have been a conflict with a mismatched version dependency on that app for the dotnet-aspnetmodule-v2 where I need the 16.x version for CCM but I accidentally upgraded to the 17.x version. At the moment the issues hasn't recurred since the day I reported it and I'm hoping having fixed that dependency has fixed the issue. I found some other things that mention local sql aliases needing to exist, I do use many dns aliases in the server's config so I might try making those as sql named pipe aliases to see if that makes any difference, though it seems a long shot.

Hi @justin-zollar_1098 , At first, it looks like debug-level logging is enabled, so I would definitely disable that under Admin > Advanced Settings > Diagnostics.MinimumLogLevel. It should be 20. The most common reason for a SQL Timeout (i.e. if you google the problem) is a SQL query that is taking too long. That shouldn't happen in Otter, but it sometimes does, especially when there is a lot of data and some non-optimzed queries. A SQL Timeout when starting the Otter Service is unusual, and it may not be related to SQL queries. The first thing I would check... are these queries actually taking that long to run in the database? You can use a tool like SQL Server Profiler or resource monitor, which will show you what's going on. You can then try running those queries directly against the database, and see if they're also taking an eternity. It's very possible that SQL Server isn't the issue at all. It could be network related - and we've even seen some bad Windows updates trigger some strange side-effects to the Windows wait handles. Best, Steve

Hi @Dan_Woolf, so it seems to be a long known issue: https://github.com/NuGet/Home/issues/3116 Thank you for your help. Caterina

Hi @jerome-virot_4088 , Linux does not support UNC paths, so you'll need to mount the appropriate machine and drive to a local directory under the Linux OS. Once this has been done, you can then map the volume in your Docker container, and configure the Drop Path in ProGet. Best, Steve

@nathan-wilcox_0355 great to know! And if you happen to have a shareable script, by all means post the results here - we'd love to share it on the docs, to help other users see some real-world use case

It's hard to say, because we haven't created our 2024 product roadmap yet :) You can see when past versions were released if you are curious: https://inedo.com/products/roadmap