More dependency graph resolver fixes #6026
Merged
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Bug
Fixes:
Description
These changes address issues found around transitive pinning and slowness when downloading packages.
When a package is transitively pinned, NuGet does not honor PrivateAssets=All and instead just adds those packages.
To make package downloads happen in parallel, the algorithm now queues a background thread which fetches the package. Later on, the item is taken off the top of the queue and the task is awaited. This makes all packages download in parallel for any given level like the legacy algorithm.
I also fixed an issue where the new algorithm was merging runtimes more than was necessary. It now uses a HashSet to keep track of which frameworks we have already processed runtime graphs for.
I've tested this with an experimental VS insertion and there is only one regression that we're going to get an exception for.
PR Checklist