-
Notifications
You must be signed in to change notification settings - Fork 258
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Need for better numbered warning message when GPR feed cannot be authenticated #8889
Comments
So while NuGet can raise a message whenever we can't authenticate (I'd expect a different message when we 401), the message that you have in particular simply cannot be coded, because it's something that GPR sets in their response headers. Worth investigating/driving to a conclusion, just setting expectations here. |
I'm laying the foundation for this with my work for #9688 |
Pretty sure it's a V3 feed. See https://nuget.pkg.github.com/nuget/index.json |
yes, my mistake there - it is v3. |
Current behavior (using the bits with my fix for 9688) - which is likely the same as shipping nuget.exe: MSBuild auto-detection: using msbuild version '16.8.0.35702' from 'C:\Program Files (x86)\Microsoft Visual Studio\2019\IntPreview\MSBuild\Current\Bin'. |
github works differently in the auth error case because when you try to fetch the feed url: https://nuget.pkg.github.com/rrelyea/index.json (for example), you are asked to auth. @anangaur - can you work with them to report this behavior, which should likely be fixed by them. once they do, the code path for failures will be identical to Azure Artifacts that I'm improving now. |
@whitneyimura, can you help redirect? |
I have GPR feed in my sources. When it could not authenticate, I get an
undefined
warning message.Expected
Better numbered warning message.
The text was updated successfully, but these errors were encountered: