fix: module consensus version is not correctly set when upgrade after state sync #391
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.
Description
Fix upgrade initializers are not called when state sync.
Rationale
If pre initializers are not called, it will lead to apphash mismatch issue. For example,
When doing migration, the to version (will be stored) is read from app.
However, when doing state sync, it will not call all previous upgrade initializers, leading to
toVersion
is not correct.Example
NA
Changes
Notable changes:
Potential Impacts
Test
Before fix:
After fix: