-
Notifications
You must be signed in to change notification settings - Fork 1.1k
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
dotnet restore stalls and prints a lot of things #6168
Comments
@smoothdeveloper you seem to be running on Win7. Do you have Virtual Box installed? Or similar? If so, you are probably running into this (known) issue: #5311 . Can you check to see if that solves your problem? |
@blackdwarf thanks for insight. I do have VMWare installed, which indeed creates extra network adapters. Are we talking about a networking issue low in the dotnet core stack (HAL or managed network socket lib)? In order to reproduce the issue, I need to clean up my nuget cache, but I have no clue where |
@smoothdeveloper could be, the Nuget team is still investigating, as you can see in the linked issue. To see if this solves your issue, just disable those virtual adapters and re-run The NuGet cache is in your home directory on Windows under |
@blackdwarf, any idea of which upstream ticket on NuGet/NuGet.Client (make sure the capital letters are consistent to make it work on linux, although GitHub Inc. is lenient on that) we should track?
We should "trickle-up" to the source of truth (NuGet.Client), and have the maintainers work on :
Thanks! |
dotnet/cli#3229 reduces the verbosity of NuGet during |
Steps to reproduce
Expected behavior
Actual behavior
Environment data
dotnet --info
output:Just for your information, to compare user experience I created this text file with edlin.exe (format is so simple that I don't need anything better):
paket.dependencies
called
paket.exe install
next to itand here is the (entire) output that got printed, I just paste it because unlike the other one I've attached, it can be printed without scaring :
paket is a community project, maintained by volunteers on their free time, you might consider contributing to it and integrate it in the
dotnet restore
story; so far it does the job better than thedotnet restore
I tried.Paket has a lots of other goodies too.
The text was updated successfully, but these errors were encountered: