runtimeverification / runtimeverification/haskell-backend
Backend gets stuck applying `#Ceil` rule for Maps
Nobody has claimed this yet.
- Dominant language
- Haskell
- Stars
- 224
- Forks
- 43
- PR merge metrics
- No merged PRs in 30d
Description
The proof I'm running gets stuck in an execute request deep in the execution, with no progress made after at least 10 hours. The bug report has been shared on Slack. According to @jberthold,
FWIW the loop occurs after 2593 steps. I have extracted the state at that point (attached). If you send that state in an execute request (rpc-client execute state-at-2593.json) it will
- immediately abort in booster (after 0 steps)
- fall back to kore, which will get trapped in a simplification loop
The rules that get repeatedly applied are
definition.kore:146565:24 domains.md:452:8-452:165
(the domains.md rule up to 3 times before the other one fires again, in my observations)
The rule in definition.kore is a #Ceil rule, and the one in domains.md relates to in_keys. They don't seem to be caught in a loop, but they are repeatedly applied, maybe because of the size and number of maps in the configuration. The maps are mostly concrete, but have a few entries with a symbolic variable.
Contributor guide
No contributing guide indexed for this repository
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 reproducing the issue with rpc-client execute state-at-2593.json and observe the booster abort followed by the Kore simplification loop. Read the repeatedly applied rules at definition.kore:146565:24 and domains.md:452:8-452:165, then verify that the execute request makes progress instead of looping.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- haskell
- Domain
- backend
- Issue type
- Bug
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100