Replies: 1 comment
-
Hi! From what I can tell, yarn v1 (the version you're using) does not support inserting commands in arbitrary positions. Yarn v2 might have added support, judging by the discussion on this link. https://stackoverflow.com/questions/50835221/pass-command-line-argument-to-child-script-in-yarn As you can see, the command generated for your example turned out to be invalid (note the stray "TestSwapFactory" in the end, and the literal $1)
Consider using this alternative: "check-assertion": "echidna . --test-mode assertion --config echidna_config.yaml --contract" // the argument with the name will be user-provided |
Beta Was this translation helpful? Give feedback.
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
Describe the issue:
When using shell-scripting passing the command-line argument, it will not work properly.
Hardcoded arguments work properly, i.e.:
"check-assertion": "echidna . --contract TestSwapFactory --test-mode assertion --config echidna_config.yaml"
Code example to reproduce the issue:
"check-assertion": "echidna . --contract $1 --test-mode assertion --config echidna_config.yaml"
Version:
Echidna 2.2.1
Relevant log output:
Beta Was this translation helpful? Give feedback.
All reactions