dotnet restore doesn't respect --disable-parallel
Open
Nobody has claimed this yet.
bug
- Dominant language
- F#
- Stars
- 2.1k
- Forks
- 528
- Avg merge
- 1d 12m
- Merged PRs (30d)
- 54
Description
Description
Running dotnet restore --disable-parallel on a Paket-enabled solution still runs in parallel. This leads to Paket fighting other instances of itself.
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 dotnet restore --disable-parallel on a Paket-enabled solution, then trace the restore handling for the disable-parallel option. Done means the command no longer runs competing Paket instances in parallel when the option is supplied.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- fsharp
- Domain
- tooling
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100