Nuget passthrough doesn't appear to be working for new packages

scott.mccollough_2525

I'm not sure exactly when this started but the pass through to nuget.org to pick up new packages seems to be broken.

C:\Program Files\dotnet\sdk\3.1.201\NuGet.targets(124,5): error : The feed 'repositoryPath [https://proget.bowl.com/nuget/Nuget/]' lists package 'Microsoft.EntityFrameworkCore.3.1.3' but multiple attempts to download the nupkg have failed. The feed is either invalid or required packages were removed while the current operation was in progress. Verify the package exists on the feed and try again. [E:\Build021_work\364\s\ResourceAccess\Setup\Usbc.ResourceAccess.Setup.Fabric.Host\Usbc.ResourceAccess.Setup.Fabric.Host.csproj]
C:\Program Files\dotnet\sdk\3.1.201\NuGet.targets(124,5): error : Unable to find package 'Microsoft.EntityFrameworkCore.3.1.3'. [E:\Build021_work\364\s\ResourceAccess\Setup\Usbc.ResourceAccess.Setup.Fabric.Host\Usbc.ResourceAccess.Setup.Fabric.Host.csproj]

I can manually add the new packages to proget via nuget.org but automatically through the build process is broken.

I suspect it started happening with version 5.3 but I'm not sure.

I did try rolling back to the latest version 5.2.x but there's no downgrade path and manually uninstalling and reinstalling resulted in a sql error on the new install. Luckily I had a snapshot to fall back on.

atripp

Hello; I'm not able to reproduce this.

I can successfully download Microsoft.EntityFrameworkCore 3.1.3 without an issue from ProGet 5.3.0-m5.

Can you navigate to the package in your instance, and hit the Download button?

Maybe it was a temporary NuGet outage?

scott.mccollough_2525

@atripp This has been happening since last friday. Old packages that are already in cache work fine. New packages are not pulling from nuget.org.

An example from this morning: Our build requires Microsoft.EntityFrameworkCore.Analyzers 3.1.3 but when I look at the files in ProGet, the latest version listed is 3.1.2 and it will not pull 3.1.3 automatically. However, if I manually add version 3.1.3 through the proget ui, the build passes that restore and fails on the next NEW package.

Our nuget.config is:

<?xml version="1.0" encoding="utf-8"?>
<configuration>
  <solution>
    <add key="disableSourceControlIntegration" value="true" />
  </solution>
  <packageSources>
    <add key="ProGet" value="https://proget.bowl.com/nuget/Nuget/" />
    <add key="nuget.org" value="https://api.nuget.org/v3/index.json" />
  </packageSources>
  <config>
    <add key="DefaultPushSource" value="https://proget.bowl.com/nuget/Nuget/" />
  </config>
</configuration>

I added the nuget.org package source this morning and the build completes now but it kind of defeats the purpose of proget as it's bypassing our local source when it can't find a package. The build completed but Proget still does not list 3.1.3 for Microsoft.EntityFrameworkCore.Analyzers

scott.mccollough_2525

@atripp I just noticed out yarn feed seems to be pulling in packages just fine.

Something else I tried was changing the nuget connector to the v3 api but that doesn't seem to have made a difference.

scott.mccollough_2525

@atripp So, I was just checking my credentials on nuget.org and found this disclaimer:
NuGet.org password login is no longer supported. Please use a Microsoft account to sign into NuGet gallery.
The connector uses a username/password. Should I change this to my ms credentials?

atripp

Oh I see; in this case, please remove your credentials from the connector. They're not required for NuGet.org; ProGet does not push to connectors, only download files.

It's a common mistake and we will try to make it clear in the UI.

scott.mccollough_2525

I did that but the pass through still seems broken. I also tried re-indexing the symbol server but that didn't make a difference either.

Is there a way to roll back to version 5.2? When I tried uninstalling and reinstalling Proget it wiped all of my settings and seemed to get hung up on the sql database. I think it didn't like that I had existing feeds.

atripp

Indexing the symbol server wouldn't make a difference. I would try clearing your connector cache.

It's very unlikely that this is a regression in 5.3; this is a very common use case, nothing strange about the package, and I can't reproduce it. So it's likely configuration or network related.

To rollback, please follow the restore instructions: https://docs.inedo.com/docs/proget/installation/backing-up

scott.mccollough_2525

I noticed that the latest Proget version has a v3 connector for nuget so I added that and also re-indexed the package store, recomputed the checksums and deleted invalid packages. While running the re-indexing I encountered three errors that indicated bad packages (files in use), so I deleted all three packages, ran the re-indexing and everything appears to be working again. I suspect the problem was the bad packages in the store.

Thank you @atripp for your help in this matter.