-
Notifications
You must be signed in to change notification settings - Fork 39
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Backtraces in errors #296
Comments
This rust playground is using the thiserror example for backtrace to show how it is produced. Still requires nightly along with two features
|
https://mmapped.blog/posts/12-rust-error-handling.html The above seem to suggest a different approach than what we were taking. I am going to prototype this in Though I couldn't get the actual backtrace to print within the crate. |
In the meantime, do more logging, instrument functions. |
Closing because we have spans per connection and protocol message. |
Not having backtraces is insanely frustrating.
Two options:
Should start with a minimal example to ensure backtraces are actually be captured.
The text was updated successfully, but these errors were encountered: