-
Notifications
You must be signed in to change notification settings - Fork 9
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
Restore lost commits #172
Restore lost commits #172
Conversation
We get some Transfer events where 0 is actually transferred. We show these in decodings and logs, but we will now not show them in the balance changes list since no balance changed.
|
||
// Recover from any panics. Should be the last deferred call so it runs | ||
// first. | ||
defer func() { |
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.
Where do we expect any panics to happen?
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.
We don't expect a panic any more than any other bugs, and all currently known vectors for a panic have been fixed, but if we ever do introduce or find a panic it's preferable to recover instead of allowing the process to crash. Crashing is expensive in terms of time to start up and re-peer so clients can't immediately reconnect like they can with other websocket failures.
Merged as separate commits to preserve fixes history. |
Some commits were made to
main
and didn't get into themempool-feed-stage
branch. This PR brings over my functionality-related changes that weren't re-added in other PRs.