Restoring packages can result in pain
Nobody has claimed this yet.
- Dominant language
- F#
- Stars
- 2.1k
- Forks
- 528
- Avg merge
- 1d 12m
- Merged PRs (30d)
- 54
Description
Description
Currently I see some builds time out:
Which in itself is not a paket bug, but the experience around this "error scenario" is pretty bad. I think we need to improve the following things:
- There are no download-statistics (speed) for the various nuget servers
- We do not time-out on downloads and try again
- We block on a single package when we could download others as well (parallel downloads)
- We do not report anything in that scenario and the output just "hangs" forever without any indication of what is happening
Maybe I can tackle some of them myself long-term, but it would be nice for others to step in on these.
Reproduction
- Get a slow nuget server or upload a large package (or both)
paket restore- Wait
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by reproducing the scenario with a slow NuGet server or large package, then run paket restore and observe its output and download behavior. Review the restore flow for timeout and retry handling, parallel downloads, download statistics, and progress reporting; done means the selected improvements are implemented and the hanging scenario gives useful feedback.
Written by the indexing model from the issue text.
Assessment
- Domain
- cli, devtools
- Issue type
- Bug
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 25/100