-
Notifications
You must be signed in to change notification settings - Fork 2.3k
feat: forge verify-bytecode should automatically recompile upon running #12651
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
base: master
Are you sure you want to change the base?
Conversation
|
I tried running: make build
make prMany tests were failing before my change, most not related to my change. Is there a guide to run all testcases smoothly? |
@Jds-23 just kicked CI and all seems good, you probably experience issues locally due to etherscan and other providers rate limiting |
grandizzy
left a comment
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I think this makes sense, small nit re test. pending @zerosnacks
zerosnacks
left a comment
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Makes sense, updated PR to inline the test
Resolves #12644
Motivation
Solution
Removed the code that checks for a cache and builds from it in
crates/verify/src/bytecode.rs.Added test that validates recompilation on source change: Builds with correct source (creates cache), replaces source with different code, runs verify-bytecode which recompiles (not using stale cache) and detects bytecode mismatch.
I consulted Claude Code to understand the codebase, but the solution was fully authored manually by me.
PR Checklist