-
Notifications
You must be signed in to change notification settings - Fork 1.8k
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
Panics, crashes if using cached output when compiling with 0.8.17 & 0.8.18 #4320
Comments
Does this only happen when switching versions? I see some leftover panics in that code section that should be removed. Would you happen to have a repro for this? does the could you please run with |
Yeah you can pull this branch Uniswap/permit2#183 |
|
thank you! checking |
this seems to be a multi version bug, need to debug this a bit more. I was able to solve the problem by making these changes to your PR this makes all used pragmas semver compatible with 0.8.18 |
okay I believe it's related to this will fix asap |
Ah ok and will that fix enable us to do versioning without carets? Purposefully have locked those contracts to the strict version without the caret. |
found the bug, only need to apply some changes to the linking step, but will ship the fix once the PR is merged. |
Component
Forge
Have you ensured that all of these are up to date?
What version of Foundry are you on?
forge 0.2.0 (249538f 2023-02-09T00:13:54.988187Z)
What command(s) is the bug in?
forge test, forge build, forge snapshot
Operating System
macOS (Apple Silicon)
Describe the bug
Running
forge build --force
compiles contracts with 0.8.17 & 0.8.18 with no issues but runningforge test
orforge snapshot
orforge build
after that will panic/crash.Also doing
forge clean && forge snapshot
gives same error.Also this is running with the backtrace
━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━ BACKTRACE ━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
1: __mh_execute_header
at :
2: __mh_execute_header
at :
3: __mh_execute_header
at :
4: __mh_execute_header
at :
5: __mh_execute_header
at :
6: __mh_execute_header
at :
7: __mh_execute_header
at :
8: __mh_execute_header
at :
9: __mh_execute_header
at :
10: __mh_execute_header
at :
11: __mh_execute_header
at :
12: __mh_execute_header
at :
13: __mh_execute_header
at :
14: __mh_execute_header
at :
15: __mh_execute_header
at :
16: __mh_execute_header
at :
The text was updated successfully, but these errors were encountered: