Skip to content
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 appears to hang on slow connections #14813

Closed
gbaydin opened this issue Dec 2, 2020 · 2 comments
Closed

dotnet restore appears to hang on slow connections #14813

gbaydin opened this issue Dec 2, 2020 · 2 comments

Comments

@gbaydin
Copy link

gbaydin commented Dec 2, 2020

Hello, I would like to bring the following issue to this repository because this is a dotnet CLI issue significantly affecting user experience in a bad way. To report the issue, I first visited https://github.com/dotnet/cli and then I was directed here from the readme there.

The problem was first brought up in 2017 in the NuGet/Home#4346 issue by @shanselman and others but was not addressed. Earlier this year I shared my problem in that same issue, but received no response. I'm copying the issue below.


Hello, I was wondering whether there has been any progress in adding a simple progress bar to dotnet restore. We're currently working on machine learning code (DiffSharp, TorchSharp) that depend on very large nuget packages (some GBs) that hold CUDA binaries, for example the following package and its dependencies:

https://www.nuget.org/packages/libtorch-cuda-10.2/

and the user experience of dotnet restore is not great because it "hangs" for long periods of time (say, half an hour in my average broadband home connection in the UK) without showing any indication of what is going on. Similar workflows in other ecosystems (say, Python pip, conda etc., or Docker) show progress information during package download showing the progress for the file currently being downloaded, download speed, ETA, etc. I think dotnet restore really needs such basic progress information in the CLI out of the box with the default settings.

I don't know if this is the correct project to report this problem (this existing issue seemed relevant). Please let me know if I should be opening an issue somewhere else, for example https://github.com/dotnet/sdk

Also tagging @dsyme @interesaaat

I'm using dotnet CLI tools on linux. This is the output of dotnet --info if it helps:

.NET Core SDK (reflecting any global.json):
 Version:   3.1.201
 Commit:    b1768b4ae7

Runtime Environment:
 OS Name:     ubuntu
 OS Version:  20.04
 OS Platform: Linux
 RID:         linux-x64
 Base Path:   /usr/share/dotnet/sdk/3.1.201/

Host (useful for support):
  Version: 3.1.3
  Commit:  4a9f85e9f8

.NET Core SDKs installed:
  3.1.201 [/usr/share/dotnet/sdk]

.NET Core runtimes installed:
  Microsoft.AspNetCore.App 3.1.3 [/usr/share/dotnet/shared/Microsoft.AspNetCore.App]
  Microsoft.NETCore.App 3.1.3 [/usr/share/dotnet/shared/Microsoft.NETCore.App]

To install additional .NET Core runtimes or SDKs:
  https://aka.ms/dotnet-download

Originally posted by @gbaydin in NuGet/Home#4346 (comment)

@gbaydin
Copy link
Author

gbaydin commented Dec 2, 2020

Note that this is still a problem with dotnet sdk 5.0.100 which I'm currently using on Linux. I would like to emphasize that implementing any of the suggestions by @shanselman in the issue NuGet/Home#4346 would solve the problem and significantly improve the user experience.

@marcpopMSFT marcpopMSFT added the untriaged Request triage from a team member label Apr 6, 2021
@sfoslund sfoslund removed their assignment Apr 7, 2021
@sfoslund sfoslund added Area-NuGet and removed untriaged Request triage from a team member labels Apr 7, 2021
@ghost
Copy link

ghost commented Apr 21, 2022

Thanks for creating this issue! We believe this issue is related to NuGet tooling, which is maintained by the NuGet team. Thus, we closed this one and encourage you to raise this issue in the NuGet repository instead. Don’t forget to check out NuGet’s contributing guide before submitting an issue!

If you believe this issue was closed out of error, please comment to let us know.

Happy Coding!

@ghost ghost closed this as completed Apr 21, 2022
This issue was closed.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

3 participants