Improve printing of backtrace in log message#124
Merged
findmyway merged 1 commit intoApr 27, 2026
Conversation
The output of `catch_backtrace()` will be shown as raw pointers when being serialized (e.g. when looking at logs in Sentry). This can be avoided by wrapping it in `stacktrace`.
krynju
pushed a commit
to krynju/OpenTelemetry.jl
that referenced
this pull request
May 25, 2026
Patch release following oolong-dev#124 (improve backtrace printing in log message). Co-Authored-By: Claude Opus 4.6 (1M context) <[email protected]>
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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
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.
The output of
catch_backtrace()will be shown as raw pointers when being serialized (e.g. when looking at logs in Sentry). This can be avoided by wrapping it instacktrace.