Fixed deadlock on IsNuGetPublished #152
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.
Whenever IsNuGetPublished is used with a source that returns a non-200 HTTP result, IsNugetPublished deadlocks and cake script stalls.
Description
Getting general resource information from the NuGet repository is not caught, failing in background. Happens with any non-200 HTTP result. Error is now trapped and dismissed in same way as other errors when fetching dependency info of the package.
Logging was added so users can see the actual error when using
Diagnostic
verbosity.Original issue can be easily replicated with the following script:
Motivation and Context
We are using private nuget repositories, which require user/password auth. API was replying with 401 causing the cake script to stall.
How Has This Been Tested?
Published locally and tested with our own private nuget repository.
Screenshots (if appropriate):
Types of changes
Checklist: