[3.2 -> 4.0] Use block_num for interrupt of start_block #908
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
…eceiving block before beginning of start_block
[3.2] Use block_num for interrupt of start_block
…pt-start-block-4.0
greg7mdp
approved these changes
Mar 27, 2023
linh2931
approved these changes
Mar 27, 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.
Signal received block with the block number so that
start_blockcan be interrupted even if the block is received before the start ofstart_block. This is particularly important for #867, but also useful as mitigation against race condition of receiving block right before start of the block in current implementation. See #648.Merges #893 into
release/4.0. Includes integration into the new ro_trx_queue (see 9e79e82).Resolves #891