We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
Forge
forge 0.2.0 (7922fd5 2024-02-05T00:19:20.258041000Z)
forge test
macOS (Intel)
This issue is a follow-up issue of this one, but since that one is old, I'd like to issue a new one.
It seems 0x0000000000000000000000000000000000000001 is a contract automatically created by foundry, but not labeled in traces:
0x0000000000000000000000000000000000000001
[0] 0x0000000000000000000000000000000000000001::fallback{value: 1000000000000000000}()
It can be reproduced here by running forge test --mp test/BatchInbox.t.sol -vvv
forge test --mp test/BatchInbox.t.sol -vvv
The text was updated successfully, but these errors were encountered:
here's the list of precompiles, probably can be labeled with Forge-{Name} for clarity? https://book.getfoundry.sh/misc/precompile-registry
Forge-{Name}
Sorry, something went wrong.
Successfully merging a pull request may close this issue.
Component
Forge
Have you ensured that all of these are up to date?
What version of Foundry are you on?
forge 0.2.0 (7922fd5 2024-02-05T00:19:20.258041000Z)
What command(s) is the bug in?
forge test
Operating System
macOS (Intel)
Describe the bug
This issue is a follow-up issue of this one, but since that one is old, I'd like to issue a new one.
It seems
0x0000000000000000000000000000000000000001
is a contract automatically created by foundry, but not labeled in traces:It can be reproduced here by running
forge test --mp test/BatchInbox.t.sol -vvv
The text was updated successfully, but these errors were encountered: