feat(cli): enable backtrace on panic by default #5942
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
shekhirin
added
C-enhancement
shekhirin
changed the title
mattsse
approved these changes
Jan 4, 2024
Comment on lines
+12
to
+15
| // Enable backtraces unless a RUST_BACKTRACE value has already been explicitly provided. | ||
| if std::env::var("RUST_BACKTRACE").is_err() { | ||
| std::env::set_var("RUST_BACKTRACE", "1"); | ||
| } |
There was a problem hiding this comment.
should we do this for the OP bin as well?
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.
RUST_BACKTRACE=1only affects the backtrace reporting on panic. Unless explicitly disabled, we want to see full backtraces when an unexpected panic occurs.Thanks sigp/lighthouse@58012f8