Print exception stacktrace from command run into stderr #14522
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
memsharded
approved these changes
Aug 18, 2023
There was a problem hiding this comment.
Yes, you are right, this better go to stderr. Thanks for this fix @BobIsOnFire!
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.
Changelog: Bugfix: Print exception stacktrace (when
-vtraceis set) into stderr instead of stdoutDocs: Omit
Hi! A
ConanExceptionfrom some command likeconan <cmd> -v trace -f json > output.jsonredirected my error into JSON file and didn't write anything into the console. I believe such output should be always written into stderr.