Merged
Conversation
…o fix/blockhash-mismatch
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
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.
This PR has a lot of little things.
Most importantly it closes #558. We now store a
BaseBlockContextthat holds the block number/timestamp when the block is first created. When you are cloning a block, you clone it with the base block context. Thus, you can allow warp and roll to update the block context while still preserving the original values.Closes #551. We fixed how context cancellations were handled across the fuzzer and its workers.
Closes #556. We now improve logging before a call sequence is shrunk
Closes #562. We can now solve this edge case by updating how fixed byte arrays are generated.
Closes #547. We are deprecating the
difficultycheatcode because we are using a post-Paris EVM version. Thus,difficultyis a no-op. We also introducedprevrandaoto update theblock.prevrandao.There was also a bug with logging optimization mode test cases. It's now fixed.
Finally, we updated some of the documentation because it was out of date.