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 (24abca6 2024-01-16T00:22:43.818205838Z)
forge test
Linux
The following code:
address d = deployCode( './foundry-out/NounsDescriptorV2.sol/NounsDescriptorV2.json', abi.encode(address(0), address(0)) );
fails with the following error:
[FAIL. Reason: setup failed: data did not match any variant of untagged enum Bytecode at line 1 column 34294] setUp() (gas: 0)
I've attached the json file.
NounsDescriptorV2.json
The text was updated successfully, but these errors were encountered:
the issue here is that your bytecode is still unlinked
I think we should add support for linking bytecode via cheatcodes here
Sorry, something went wrong.
@mattsse thanks for the quick diagnosis!
any estimate on when support for linking bytecode will be available? any workaround we can use in the meantime?
any estimate on when support for linking bytecode will be available?
just checked this is a known feature request, can try to bump prio for this #6120
workaround would probably be to deploy the linked library first then replace in the code, or do this via an ffi command
Closing as duplicate of #6120.
No branches or pull requests
Component
Forge
Have you ensured that all of these are up to date?
What version of Foundry are you on?
forge 0.2.0 (24abca6 2024-01-16T00:22:43.818205838Z)
What command(s) is the bug in?
forge test
Operating System
Linux
Describe the bug
The following code:
fails with the following error:
I've attached the json file.
NounsDescriptorV2.json
The text was updated successfully, but these errors were encountered: