fix: syncer spamming RPC and reaching tip of chain#289
Merged
joanestebanr merged 4 commits intorelease/v0.5.1from Jan 30, 2025
Merged
fix: syncer spamming RPC and reaching tip of chain#289joanestebanr merged 4 commits intorelease/v0.5.1from
joanestebanr merged 4 commits intorelease/v0.5.1from
Conversation
|
ToniRamirezM
approved these changes
Jan 29, 2025
goran-ethernal
approved these changes
Jan 30, 2025
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
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.



When any synchronize exceeds the block finalized keep asking continously for same range without any sleep, and don't extend the range to reach the lastest block
expected
Here the explanation of how must work the range when we are > finalized:
Ask logs for current range [ n - m ]