fix: bug block not been processed yet #302
Merged
+453
−315
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
ToniRamirezM
approved these changes
Feb 21, 2025
…in fork configurations
Stefan-Ethernal
force-pushed
the
fix/getting_sequences_block_have_not_been_processed_yet
branch
from
1083ec7 to
c498e4f
Compare
|
joanestebanr
deleted the
fix/getting_sequences_block_have_not_been_processed_yet
branch
Closed
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.
Description
Sequencer Sender take more than expected to submit a new sequence. The logs shows next reason:
This is because there are an error on downloaderriver that have a high occurence when the sync finality is finalizedBlock.