Correctly update computer digest when state of contract 0 is changed #84
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
|
looks good to me, let test this on test net next few days to confirm the issue is gone |
philippwerner
added a commit
that referenced
this pull request
Apr 9, 2024
…84) * When contract 0 state is changed, set flag for updating digest * Wrap fee reserve change into function
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.
When contract 0 state is changed, set flag for updating digest.
This fixes an issue that led to misalignment between nodes that survived the seamless epoch transition at April 3, 2024 (no full update of computer digest) and nodes that were restarted (forced full computing of computer digest after reloading contract files).