-
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
[Bug]: NuGet package parsing fails #11879
Comments
I have same problem, when try to restore project in Docker. |
I am also seeing these kinds of errors. Yesterday I had pipelines working no problem, and then suddenly they started failing even though no changes were made to the packages or any other Nuget configurations. Here is the pipeline error I am seeing a lot (the package name that fails is random):
Sometimes if I try to follow the URL in my browser I get valid JSON back. Other times I get XML back with a "BlobNotFound" error in the details, but like I said it's totally random. |
Same here. Fails quite often but not always. |
I am also having issues when running in docker. No problems with host. I am getting following error with nslookup
|
I'm getting this only while running from our build server, only for one package. All logged lines for the Hangfire.InMemory package copied below. I'm able to restore this package locally on windows, in a Ubuntu WSL2 after clean and clearing nuget caches. The URL opens just fine for me. We just started seeing this within the last day.
|
Same here. Doesn't always fail but seems to most of the time |
Hello, thanks you for taking the time to report this. This is a duplicate of NuGet/NuGetGallery#9140. We'll use that one issue to track the api.nuget.org connectivity problem as well as the JSON corruption issue. As of now, we have performed a failover for our CDN provider which we expect to mitigate the problem. If you are still facing a problem, please post on the issue I linked above. |
Hi @joelverhagen I can't get Microsoft, Nuget, or Google packages although they are specified in my |
Hey @bakgaard, what you're describing appears to be related to the Could you open a separate issue on NuGet/Home with your config, the error message, SDK version, etc? I suggest NuGet/Home not NuGet/NuGetGallery since that's a client feature. Since it's impacting the success of your workflow we should involve the NuGet client team first instead of the NuGet server team. |
NuGet Product Used
dotnet.exe
Product Version
3.1.x
Worked before?
3.1.x
Impact
It's more difficult to complete my work
Repro Steps & Context
nuget restore
on a package using Pulumi, and voila:I've seen this error cause at least 3 build pipelines to fail. The two above I had in open tabs, there almost certainly are more failures that I haven't directly observed.
See also:
Verbose Logs
No response
The text was updated successfully, but these errors were encountered: