runtimeverification / runtimeverification/kontrol
Toggling verbosity during proof for HCI
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 122
- Forks
- 16
- PR merge metrics
- No merged PRs in 30d
Description
Problem
Proofs with kontrol often take several minutes, if the --verbose flag is initially omitted (and without --use-booster) then the terminal has no change until either the proof fails or succeeds. This leaves a lot of time for people to grow concerned about whether the program has crashed or is indeed silently working.
Solution
It would be nice if pressing a key could toggle verbose input during an executing proof. That way a person who is tempted to stop the proof and rerun with --verbose will likely be satisfied by seeing the rpc requests. Not sure how feasible it would be to implement with the current architecture, but maybe it would not be too hard with a signal handler. I also realise that now it should not be a problem stopping and starting proofs with the same version as the progress is saved.
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
No files or tests are named in the issue. Start by tracing how kontrol runs proofs, handles --verbose and --use-booster, and reports RPC requests in the terminal. Define the interaction and interruption behavior, then verify that verbosity can be toggled during an executing proof without stopping it.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- cli
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100