fix(forge): loadAllocs
cheatcode doesn't persist when called in setUp
#6297
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.
Overview
The
loadAllocs
cheatcode currently does not persist loaded account information if it is called in thesetUp
function. This is because none of the loaded accounts were marked as touched during the loading process.Solution
Touch each account that is loaded into the
revm
journal in theload_allocs
function in the DB backend.Tests
Added a regression test for the fixed bug, asserting that the loaded accounts are persisted when the cheatcode is called in
setUp
.