Skip to content
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

Merged
merged 7 commits into from
Apr 2, 2024
Merged

Restore lost commits #172

merged 7 commits into from
Apr 2, 2024

Conversation

tyler-smith
Copy link

@tyler-smith tyler-smith commented Mar 25, 2024

Some commits were made to main and didn't get into the mempool-feed-stage branch. This PR brings over my functionality-related changes that weren't re-added in other PRs.

  • Trace stream API metrics
  • Trace stream API panic recovery
  • Don't attempt getting token metadata without tokenID
  • Bug fix for transfer events with 0 value (NBC)
  • Bug fix for gas transfer handing (NBC)

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.
@tyler-smith tyler-smith changed the title Ts restore Restore lost commits Mar 25, 2024
@tyler-smith tyler-smith marked this pull request as ready for review March 25, 2024 07:58

// Recover from any panics. Should be the last deferred call so it runs
// first.
defer func() {
Copy link

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?

Copy link
Author

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.

@lukanus lukanus merged commit 755dd73 into mempool-feed-stage Apr 2, 2024
1 check passed
@lukanus
Copy link

lukanus commented Apr 2, 2024

Merged as separate commits to preserve fixes history.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants