C#: Gracefully handle dotnet --info exit code 143.
#20936
Draft
+50
−7
Conversation
This file contains hidden or 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
michaelnebel
changed the title
dotnet --info failure.
michaelnebel
force-pushed
the
csharp/nocrashdotnetinfo
branch
from
e425d75 to
af64e33
Compare
michaelnebel
changed the title
dotnet --info failure.dotnet --info exit code 143.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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.
Instead of crashing the dependency fetcher in case
dotnet --infogets killed (exit code143), it is just reported as a warning.@hvitved : I am all open for other suggestions as this is not ideal.