blockstore, geyser: handle corrupt blocks without killing the validator #3750
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
lidatong
reviewed
Dec 19, 2024
topointon-jump
force-pushed
the
topointon/premature-end-of-block
branch
from
8a6cc9e to
231e982
Compare
lidatong
approved these changes
Dec 19, 2024
topointon-jump
force-pushed
the
topointon/premature-end-of-block
branch
from
231e982 to
5e1ee28
Compare
|
closing in favour of #3808 |
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.
If we are sent a corrupt shred we should not exit the validator, but throw the shred away and continue.