This repository has been archived by the owner on Oct 25, 2024. It is now read-only.
Efficient reverts clean dirty state cache #102
Merged
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.
📝 Summary
Fixes bug in efficient reverts branch.
There is a bad interaction between our multi tx snapshot and journal that is used to revert changes for internal calls. That was happening because accounts that were changed and then reverted according to journal were not considered "dirty" when finalizing so their dirty state was not cleaned.
Later this state would be used for state root calculation when finalized for each object is called too.
This adds a unit test that was failing before these changes were introduced.
CONTRIBUTING.md