Skip to content
New issue

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

Parser error when passing string as parameter to script #6265

Closed
2 tasks done
PaulRBerg opened this issue Nov 9, 2023 · 2 comments · Fixed by #6269
Closed
2 tasks done

Parser error when passing string as parameter to script #6265

PaulRBerg opened this issue Nov 9, 2023 · 2 comments · Fixed by #6269
Labels
T-bug Type: bug

Comments

@PaulRBerg
Copy link
Contributor

Component

Forge

Have you ensured that all of these are up to date?

  • Foundry
  • Foundryup

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:

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.

@PaulRBerg PaulRBerg added the T-bug Type: bug label Nov 9, 2023
@PaulRBerg
Copy link
Contributor Author

Replacing the comma (,) with a colon (:) worked.

@PaulRBerg
Copy link
Contributor Author

PaulRBerg commented Dec 17, 2023

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

Nevermind

Sorry guys, false alarm. See #6050 (comment).

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
T-bug Type: bug
Projects
Archived in project
Development

Successfully merging a pull request may close this issue.

1 participant