Trace detailed messages for missing package errors #3001
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
If the resolver goes to a retry, or fails completely, trace a more detailed message which can be usable for immediate investigation
1/ Warning "Trial1 (NuGet.GetVersions) did not yield any results" did not contain any exact information -- added the failing request/s
2/ Failure "Unable to retrieve package versions" did not contain information needed to discover how the missing package was requested at all -- added readable open/closed requirement report
This seems to be enough to see the issue at hand without resorting to verbose and lengthy analysis in many cases