runtimeverification / runtimeverification/evm-semantics
Cannot supply custom `--kore-rpc-command` to `kevm foundry-prove`
Nobody has claimed this yet.
- Dominant language
- KCL
- Stars
- 591
- Forks
- 156
- Avg merge
- 2h 19m
- Merged PRs (30d)
- 1
Description
When calling kevm found-prove, kevm does not have access to neither kore-rpc-booster nor even kore-rpc.
An attempt to provide a trivial custom command fails as follows (shortened):
cd test/foundry
...
$ kevm foundry-prove --verbose --test AccountParamsTest.testDealConcrete --kore-rpc-command 'kore–rpc'
...
INFO 2023-08-23 12:10:40,636 pyk.kore.rpc - Starting KoreServer: kore–rpc out/kompiled/definition.kore --module FOUNDRY-MAIN --server-port 0 --smt-timeout 300 --smt-retry-limit 10
...
FileNotFoundError: [Errno 2] No such file or directory: 'kore–rpc'
The command works as expected if given an absolute path to kore-rpc/kore-rpc-booster`:
$ kevm foundry-prove --verbose --test AccountParamsTest.testDealConcrete --kore-rpc-command '/nix/store/<LONG_STRING>/bin/kore–rpc'
...Normal output...
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by reproducing the command from test/foundry with kevm foundry-prove and trace how --kore-rpc-command reaches pyk.kore.rpc. Compare the failing command-name case with the working absolute path case; done means a valid custom kore-rpc or kore-rpc-booster command can be supplied without requiring an absolute path.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- cli
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100