tx.origin prank does not persist through nested message calls #1210
Assignees
Labels
A-cheatcodes
Area: cheatcodes
C-forge
Command: forge
Cmd-forge-test
Command: forge test
T-bug
Type: bug
Comments
onbjerg
added
Cmd-forge-test
onbjerg
added a commit
that referenced
this issue
Apr 6, 2022
|
Good catch, fixed in #1215 which will be released tonight if merged. In the meantime |
gakonst
pushed a commit
that referenced
this issue
Apr 7, 2022
* fix: correct depth where we check expected emits * fix: don't reset `tx.origin` too early Closes #1210
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Component
Forge
Have you ensured that all of these are up to date?
What version of Foundry are you on?
forge 0.2.0 (6130af7 2022-04-06T00:03:48.094239707+00:00)
What command(s) is the bug in?
forge test
Operating System
Linux
Describe the bug
Minimal code and steps to replicate:
https://gist.github.com/strawberry-fury/ade15e042494d9fa6a1bfac7bfbce660
After running
forge initin an empty directory, put the above code in a .sol file in src/, then runforge test.The test will fail because the
assertEqon line 43 fails, but in reality it shouldn't.If Line 31 (transfer() on the dummy ERC20) is commented out, the test passes.
This leads me to believe that it's due to the behavior that after any message call finishes, the tx.origin prank is over.
The text was updated successfully, but these errors were encountered: