[4.0 -> main] forkdb reset in replay since blocks are signaled #944
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
[3.2] forkdb reset in replay since blocks are signaled
[3.2 -> 4.0] forkdb reset in replay since blocks are signaled
linh2931
approved these changes
Mar 31, 2023
greg7mdp
approved these changes
Apr 1, 2023
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.
Fix for replay where
forkdb.root()is null during the write in SHiP foron_accepted_block. 4.0 SHiP callschain.last_irreversible_block_id()inon_accepted_blockwhich expectsforkdb.root()to be valid.Merges #936 & #938 into
mainResolves #596