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 (57180fc 2023-11-09T01:50:25.972958000Z)
forge script
macOS (Apple Silicon)
I was trying to run this script, when I got the following error:
Error: parser error: ChainID 42161, Version 1.0.0
The full command I tried to run is:
FOUNDRY_PROFILE=optimized \ forge script script/DeployDeterministicBatch.t.sol \ --broadcast \ --rpc-url arbitrum_one \ --sig "run(string)" \ --verify \ "ChainID 42161, Version 1.0.0" \ -vvvv
The error seems to be that Foundry cannot parse the string correctly.
This wasn't happening before.
The text was updated successfully, but these errors were encountered:
Replacing the comma (,) with a colon (:) worked.
,
:
Sorry, something went wrong.
This issue has to be re-opened. I am getting a similar error as before:
Deserialization Error: EOF while parsing a value at line 1 column 0. Response:
When trying to use a string that contains a comma as a constructor param, e.g.
"ChainID 56, Version 1.1.1"
We used commas in our V2.0 deployment, and we would like to use them in our V2.1 deployment, too.
Cc @DaniPopes @Evalir
Sorry guys, false alarm. See #6050 (comment).
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 (57180fc 2023-11-09T01:50:25.972958000Z)
What command(s) is the bug in?
forge script
Operating System
macOS (Apple Silicon)
Describe the bug
I was trying to run this script, when I got the following error:
The full command I tried to run is:
The error seems to be that Foundry cannot parse the string correctly.
This wasn't happening before.
The text was updated successfully, but these errors were encountered: