Use aligned block ranges in eth_getLogs requests during historical processing
#527
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
nikugogoi
changed the title
eth_getLogs requests during historical processingeth_getLogs requests during historical processing
nikugogoi
force-pushed
the
ng-aligned-block-range
branch
2 times, most recently
from
4f3911f to
a8337bc
Compare
nikugogoi
force-pushed
the
ng-aligned-block-range
branch
from
a8337bc to
6810130
Compare
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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.
Part of Investigate subgraph watchers lagging behind head
historicalLogsBlockRangeEndFactorfor setting aligned block ranges in eth_getLogsblockProcessingOffsetis set to some value