CP-49134: tracing: do not destroy stacktrace #6117
Merged
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
Reraise with the original stacktrace, this requires using the raw backtrace instead of the string one. Signed-off-by: Edwin Török <edwin.torok@cloud.com>
contificate
approved these changes
Nov 18, 2024
robhoes
approved these changes
Nov 18, 2024
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.
Reraise with the original stacktrace, this requires using the raw backtrace instead of the string one.
I had this change sitting in a branch since around Apr 25 2024, although the branch itself might need more testing, this is a simple fix that we should probably get in sooner.