runtimeverification / runtimeverification/kontrol
Save generated counterexamples for proofs
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 122
- Forks
- 16
- PR merge metrics
- No merged PRs in 30d
Description
When kontrol prove on a proof that's being reloaded and has a failed node, kore-rpc server gets started to run generate a counterexample, which takes a minute or so (which is also getting added to proof execution time: https://github.com/runtimeverification/kontrol/issues/489). This could be avoided if we saved the counterexample together with other proof artifacts.
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 reading the kontrol prove reload path and how proof artifacts are saved. Reproduce a failed-node reload and observe when the kore-rpc server starts to generate a counterexample. Done means the counterexample is saved with the other proof artifacts and reused on reload, avoiding regeneration.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- tooling
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100