-
Notifications
You must be signed in to change notification settings - Fork 39
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
fix!: replay issue when round is 0 on replay. #2091
Merged
Merged
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
…form into fix/masternodeDiffAtGenesis
…form into fix/masternodeDiffAtGenesis
shumkov
changed the title
fix: replay issue when round is 0 on replay.
fix!: replay issue when round is 0 on replay.
Aug 30, 2024
shumkov
approved these changes
Aug 30, 2024
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
👍
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.
Issue being fixed or feature implemented
There were a few pretty bad issues fixed in this PR.
First there were issues when reenabling withdrawal keys.
There were also issues when dealing with complex situations around operator identity changes.
But the most important fix is that we can now rollback to the transaction savepoint properly. Without this multiple rounds at genesis would crash the system.
What was done?
Updated to GroveDB v2.0.3
Added many tests.
A lot of fixes in Masternode identity updates.
How Has This Been Tested?
Breaking Changes
Checklist:
For repository code-owners and collaborators only