fix(sim): use previous block number for creating alloy db in simulator #119
Conversation
This file contains hidden or 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
- Commit `6499785` introduced a logic change that used the block number from the `block_env` to fetch the state for the alloy DB instance, which results in querying for state of a block number that doesn't exist. - This commit reduces that number by 1 to correctly create the AlloyDB state from the previous block instead of the in-progress block.
This stack of pull requests is managed by Graphite. Learn more about stacking. |
prestwich
approved these changes
Jun 23, 2025
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.
fix(sim): use previous block number for creating alloy db in simulator
PR #116 introduced a logic change that reused the block number from the
block_envto fetch the state for the alloy DB instance, which results in querying for state of a block number that doesn't exist.This commit reduces that number by 1 to correctly create the AlloyDB state from the previous block instead of the in-progress block.