Skip to content

[Bug-Candidate]: Cannot use command line arguments #1140

@0xneves

Description

@0xneves

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:

yarn run v1.22.19
$ echidna . --contract $1 --test-mode assertion --config echidna_config.yaml TestSwapFactory
echidna: Couldn't compile given file
stdout:
stderr:
Traceback (most recent call last):
  File "/opt/homebrew/bin/crytic-compile", line 8, in <module>
    sys.exit(main())
             ^^^^^^
  File "/opt/homebrew/Cellar/crytic-compile/0.3.5_1/libexec/lib/python3.12/site-packages/crytic_compile/__main__.py", line 221, in main
    compilations = compile_all(**vars(args))
                   ^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/opt/homebrew/Cellar/crytic-compile/0.3.5_1/libexec/lib/python3.12/site-packages/crytic_compile/crytic_compile.py", line 740, in compile_all
    raise NotImplementedError()
NotImplementedError

error Command failed with exit code 1.
info Visit https://yarnpkg.com/en/docs/cli/run for documentation about this command.

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions