Keep accurate term in history on the primary#2111
Merged
Merged
Conversation
|
term_in_history@17992 aka 20210126.29 vs master ewma over 50 builds from 17290 to 17925 |
ashamis
reviewed
Jan 25, 2021
ashamis
reviewed
Jan 25, 2021
ashamis
approved these changes
Jan 25, 2021
eddyashton
reviewed
Jan 26, 2021
eddyashton
approved these changes
Jan 26, 2021
Co-authored-by: Eddy Ashton <ashton.eddy@gmail.com>
Closed
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
3 participants
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.
Next part of #2087
This is necessary so the frontend can atomically capture a (term, version, root) and initialise the Tx with an up to date (term, read_version) and the corresponding merkle tree root.