Hi @shiv03_9800, We have just released a new version of Otter that includes a fix for the segmentation fault. You will need to make sure that .NET Framework 4.5.1 or greater is installed on the Windows server. But if you were able to run the Inedo Agent installer, then chances are you already have that installed. As for the Inedo Agent error, I talked with some colleagues and this is something we have seen on slower or congested networks when checking Inedo Agent has the components needed to communicate with Otter. Normally if you wait for the next server check to occur, the issue ends up resolving itself. There was another issue, however, that can affect PowerShell scripts when using the Docker version of Otter, OT-432. This was fixed in the latest release as well. Thanks, Rich

Correct; that, and the API key, are what get sent over.

Neat graphic! Apple Passbook epeixlmfies wallet without nfc; Samsung Galaxy Note has nfc to beam files between phones, so it would represent the left. Google is working on the intersection of nfc and wallet, so it is nice Microsoft represents another entry into the nfc wallet category!

I have tracked down the root cause of this issue. NuGet feeds (but not NuGet (quirks) feeds) in ProGet 5 generate a list of symbols, but never actually put them in the database. The fix is filed as PG-1195 and will be coming in the next version of ProGet 5. It includes a button in the feed management page to re-index all symbols in a feed, and packages affected by this bug have a message with a link to the feed management page in the place where the list of symbol files would normally be.

Hi @Evan_Mulawski_8840 , That particular bug may be resolved by running the patch script attached to this upcoming change: https://inedo.myjetbrains.com/youtrack/issue/PG-2484 As for retrying the migration; there will be a button on the ProGet root page if there is a failed/incomplete migration (/) that allows you to retry it. This will open to the /retry-migration URL, which I would recommend using instead of a database insert. Best, Dean

I see, in that case, your network/server is not properly configured. This is not trivial to troubleshoot, and this is happening before the request hits our software. The most likely culprit is an invalid/missing SPN, and a domain administrator must add that. Here are some additional resources to follow: https://support.microsoft.com/en-us/kb/969060 http://www.sidesofmarch.com/index.php/archive/2011/11/04/troubleshooting-windows-authentication-in-iis/ http://serverfault.com/questions/341978/troubleshooting-windows-authentication-problems-no-challenge-in-iis-7-5 Search terms, "diagnosing windows authentication iis"

I can confirm that its working for us now. Thanks!

Hi @inok_spb - that's correct, the proc is dropped/created each time ProGet is upgraded/installed.

@daniel-lundqvist_1790 no problem.. docker is really confusing/silly... , glad we got it solved :)

It could be that the versions were fixed up when a package cleanup ran - happens every day by default, but may not have been immediately after the upgrade. Thanks for letting us know about the zeros missing from that page; we'll add an issue for this to get fixed in the next release.

I tested the new version (local, brand-new installation) and now all corrections to version numbers are consistent. Thanks for the quick fix!

Are you sure the requests are actually leaving your desktop? Obviously The Real WTF here is doing ONE THOUSAND outbound network requests for a contiguous operation. Since they managed to write a client that does that, I think there's no chance that they can competently build a proper network request pool, let alone one that reports proper messages. The NuGet client had a problem with this a while ago, where it was doing similar nonsense that lead to race conditions that only appeared when you used ProGet b/c the requests were being served significantly faster than NuGet.org.

Sorry to resurrect my old post, but I'm trying to use LDAP in ProGet and am running into the same issue. Users and groups that are in the domain of the server running ProGet are found, but users in a different domain are not.

@atripp 5.2.27 has fixed the issue. Thank you so much!

Hello; this issue is known now, I've logged an issue and we'll get it fixed in the next release; PG-1727 Release is scheduled for Friday, but we may ship it sooner.

Created repo including working docker-compose file + some guide. https://github.com/Relers/proget-nginx

Hi @caterina, Here is the final solution: When using the auto type and scanning for NuGet and npm dependencies: The default configuration should be to omit dev dependencies and scan the node_modules directory When using the npm type and a package-lock.json file is specified The default is to only scan the specified package-lock.json file and omit dev dependencies When using the npm type and a package-lock.json file is not specified The default configuration should be to omit dev dependencies and scan the node_modules directory Each of these options would have an optional parameter to include the dev dependencies (--include-dev) Each of these options would have an optional parameter to ignore pacakge-lock.json files found under node_modules (--package-lock-only ) This has been implemented in pgscan 1.5.6 which I will be pushing shortly, and these options will be added to BuildMaster 2023.2. Thanks, Rich

Tod, XML Configuration, in fact, is as you suggested, I was only using "MyAssembly" for reference. This is how I have it. <{Company}.ProGetExtensions.FilteredPackageStore Assembly="{Company}ProGetExtensions"> </{Company}.ProGetExtensions.FilteredPackageStore> I tried to start it from command line, same error.

Thank you. I will do that.