fix(jsonrpc): use min(to, currentMaxBlock) to compare with maxBlockRange #6275
+161
−15
Conversation
This file contains hidden or 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
waynercheung
force-pushed
the
feat/harden_filters
branch
from
fd6e091 to
00fcf04
Compare
waynercheung
force-pushed
the
feat/harden_filters
branch
from
00fcf04 to
95082c2
Compare
halibobo1205
approved these changes
Apr 2, 2025
kuny0707
approved these changes
Apr 2, 2025
CodeNinjaEvan
approved these changes
Apr 2, 2025
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.
What does this PR do?
use min(to, currentMaxBlock) to compare with maxBlockRange
Why are these changes required?
When input
tois "latest", it will be set to Long.MAX_VALUE, so we need to use min(to, currentMaxBlock) to compare with maxBlockRangeThis PR has been tested by:
Follow up
Extra details