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 (0ae39ea 2023-12-11T00:27:32.487222000Z)
forge script
macOS (Apple Silicon)
On the last few nightly releases of foundry, I've been receiving the error:
2023-12-11T18:49:05.565916Z ERROR forge::cmd::script::transaction: Failed to decode constructor arguments constructor="constructor(address,string)" contract=Some("ResolvedDelegateProxy") bytecode="0x..."
This seems to be a regression of the fix introduced for #3229, and I can confirm that it was working on last week's nightly release.
Before Regression
foundryup --version nightly-5b7e4cb3c882b28f3c32ba580de27ce7381f415a && \ git clone git@github.com:ethereum-optimism/optimism.git && \ cd optimism && \ make devnet-allocs
After Regression
foundryup && \ git clone git@github.com:ethereum-optimism/optimism.git && \ cd optimism && \ make devnet-allocs
The text was updated successfully, but these errors were encountered:
From bisecting the above steps to repro it seems the issue was introduced in #6300, cc @klkvr
Sorry, something went wrong.
Closed by #6589, thanks again @klkvr!
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 (0ae39ea 2023-12-11T00:27:32.487222000Z)
What command(s) is the bug in?
forge script
Operating System
macOS (Apple Silicon)
Describe the bug
On the last few nightly releases of foundry, I've been receiving the error:
This seems to be a regression of the fix introduced for #3229, and I can confirm that it was working on last week's nightly release.
Steps to Reproduce
Before Regression
After Regression
The text was updated successfully, but these errors were encountered: