-
Notifications
You must be signed in to change notification settings - Fork 332
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
Fix crash during initialization of event monitor when node is down #895
Conversation
It seems like the WebSocketClient does not notify us when the connection goes down so we cannot print a warning and try to reconnect. Will investigate and open an issue on tendermint-rs. |
let span = error_span!("worker loop", worker = %self); | ||
let _guard = span.enter(); |
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.
nice!
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.
Great stuff!!! Thanks Romain!
…nformalsystems#895) * Introduce error type for event monitor * Do not crash if chain runtime fails to subscribe to events * Gracefully handle runtime init error in `start-multi` command * Improve worker error context * Fix chain id in error message if spawning chain runtime fails * Print channel error when one arises * Refactor event monitor loop a little bit * Update changelog
Closes: #863
Description
Follow-up
WebSocketClient
does not notify us when the connection goes down so we cannot print a warning and try to reconnect. Will investigate and open an issue on tendermint-rs.For contributor use:
docs/
) and code comments.Files changed
in the Github PR explorer.