fix(user-ops-indexer): u64 convert panic #1016
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
k1rill-fedoseev
force-pushed
the
kf/fix/user-ops-u64-panic
branch
from
744f3be to
f5c5a9c
Compare
rimrakhimov
approved these changes
Aug 16, 2024
k1rill-fedoseev
changed the title
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Fix panic for transactions with invalid gas limits that do not fit in u64 - https://base.blockscout.com/tx/0x26761bdbb17a201984859e0510eb0ae1f53616c7384fa64d9d100a49d1bd1ab8?tab=logs
Shouldn't impact API format, since u64 were serialized as string in JSON anyway.