-
Notifications
You must be signed in to change notification settings - Fork 747
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
Properly log panics with slog #5075
Conversation
beacon_node/src/lib.rs
Outdated
std::panic::set_hook(Box::new(move |info| { | ||
crit!( | ||
log, | ||
"Task panic. This is a bug!"; |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Should it suggest to contact developers / open a Github issue if this happens?
At least like in the previous version
"advice" => "Please check above for a backtrace and notify \
the developers"
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
yeah makes sense to keep it, thanks!
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM!
@Mergifyio queue |
✅ The pull request has been merged automaticallyThe pull request has been merged automatically at dada575 |
* log panics with slog * update set_hook location * Merge branch 'unstable' of https://github.com/sigp/lighthouse into slog-panics
Questions
panic::set_hook
as I am not 100% sure about it.example of logs with this PR:
thanks