runtimeverification / runtimeverification/kontrol
Make terminal output more user-friendly
Open
Nobody has claimed this yet.
enhancement
- Dominant language
- Python
- Stars
- 122
- Forks
- 16
- PR merge metrics
- No merged PRs in 30d
Description
There were two issues expressed recently wrt the output we're printing for kontrol prove:
- backend logs take lots of space in the terminal window and might look like warnings or errors to external users (OTOH, they also are useful as an indicator of progress being made)
- https://github.com/runtimeverification/evm-semantics/issues/1792: the configuration shown in the output for the failing mode contains bulky and hard-to-read items, such as bytecode of the program being run and can be reduced to most important cells, such as
calldata,PC,wordStack,memory,storage, andoutput
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
Start with the kontrol prove terminal-output entry point and review the concerns described in this issue alongside evm-semantics issue 1792. Done means backend logs remain useful without resembling warnings or errors, and failing-mode configuration output focuses on the listed important cells rather than bulky items such as bytecode.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- cli
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100