runtimeverification / runtimeverification/kontrol
Expose most common backend logging options directly to Kontrol CLI
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 122
- Forks
- 16
- PR merge metrics
- No merged PRs in 30d
Description
The kore-rpc and kore-rpc-booster logs ar ethe way we tell the user what simplifications are happening where. These logs are in Kore format, and output information about what rules apply/don't apply. Some things we can do to make using them easier:
- Add CLI option to
kontrolwhich turns on those logs. - Add utility in pyk which reads in the logs, parses the Kore terms and prints them as K terms instead.
- Add utility in pyk which structures the logs a bit, makes them foldable, etc... to be able to jump through simplifications faster.
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 by locating the Kontrol CLI entry point and the pyk utilities that handle kore-rpc and kore-rpc-booster output. Clarify the scope for enabling logs, parsing Kore terms into K terms, and structuring output for folding; done should include a defined CLI behavior and usable log-processing utilities.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- cli, tooling
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100