runtimeverification / runtimeverification/kontrol
Fix `trace-rewrites` behavior in Kontrol, KEVM
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 122
- Forks
- 16
- PR merge metrics
- No merged PRs in 30d
Description
The --trace-rewrites option available in KEVM and Kontrol activates additional logging (log-successful-rewrites, log-failed-rewrites, etc.) in the backend, which logs this information in the response from the server; to get the actual rewrite traces, the user should provide an option similar to the following:
--kore-rpc-command 'kore-rpc --trace-rewrites trace.yaml'
--kore-rpc-command 'kore-rpc-booster definition.kore --module ... -l Rewrite'
We should probably align the behavior of --trace-rewrites between Kontrol and the backend.
Contributor guide
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
Trace --trace-rewrites through the Kontrol and KEVM invocation paths, then compare its behavior with --kore-rpc-command and the backend JSON-RPC response described in the linked API documentation. Done means the option consistently produces the intended rewrite traces rather than only enabling backend logging.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- backend, cli
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100