You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
During the PR #1879 we introduced a check on the bytecode lengths during verification ie. if bytecode lengths don't match we assume these contracts don't match.
However after implementing this the test "should detect extra file input bug when optimizer is enabled" started to fail because apparently the bytecode lengths are different for the onchain contract vs. recompiled with extra files.
To my understanding this shouldn't have happened because the bug is only affecting the AST IDs, and the bytecode lengths should've stayed the same. We should investigate what the real issue is or if our understanding was wrong.
The text was updated successfully, but these errors were encountered:
During the PR #1879 we introduced a check on the bytecode lengths during verification ie. if bytecode lengths don't match we assume these contracts don't match.
However after implementing this the test "should detect extra file input bug when optimizer is enabled" started to fail because apparently the bytecode lengths are different for the onchain contract vs. recompiled with extra files.
To my understanding this shouldn't have happened because the bug is only affecting the AST IDs, and the bytecode lengths should've stayed the same. We should investigate what the real issue is or if our understanding was wrong.
The text was updated successfully, but these errors were encountered: