-
Notifications
You must be signed in to change notification settings - Fork 253
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
Missing resilience? #13540
Comments
Digging further in to this by debugging from the NuGet.Client solution, I see that the issue can be in two places:
Funny thing is that if I open the file I'm trying to push, it works fine. I can see the nuspec file just fine. And several similar packages being other versions of the same component are pushed as expected. |
Additional info. Tried to push the package with But I also did it from a Nuget.Commandline version been run from Visual Studio where I made a change to provide credentials when needed instead of providing it in Console window. |
Hey @bstordrup The Have you faced this issue with any other package registry? |
Hi @nkolev92 I did not try the The fact that the issue is completely gone with the But I cannot put a finger on what and where the issue is. |
Thanks for the quick response. The fact that we haven't seen a lot of this, makes me think there are more likely issues server side than client side. |
This issue has been automatically marked as stale because we have not received a response in 14 days. It will be closed if no further activity occurs within another 14 days of this comment. |
NuGet Product Used
NuGet.exe
Product Version
nuget 6.11.0.64
Worked before?
No response
Impact
It's more difficult to complete my work
Repro Steps & Context
Sometimes, I get this error when running
nuget push
:Then I can issue the exact same
nuget push
command again, and it succeeds without the error, and the package is pushed.It most often happen if the commands get executed too soon after each other - for example in a PowerShell script that pushes a series of nupkg's.
I suspect that there is some kind of resilience issue involved.
Verbose Logs
The text was updated successfully, but these errors were encountered: