Changing `internal.minimalSnapshots` option leads to a panic
Nobody has claimed this yet.
- Dominant language
- Lean
- Stars
- 9.2k
- Forks
- 990
- Avg merge
- 1d 17h
- Merged PRs (30d)
- 175
Description
Steps to Reproduce
- Create a Lean file containing
set_option internal.minimalSnapshots true
- Delete the final
e
Expected behavior: That there be no observable behavior.
Actual behavior: A popup containing "Lean server printed an error: PANIC at outOfBounds Init.GetElem:11:2: index out of bounds" and an error in the VS Code "Output" area reporting "PANIC at Lean.Elab.InfoTree.visitM.go Lean.Server.InfoUtils:56:21: unexpected context-free info tree node".
Versions
Lean 4.12.0 8c96d213f3089ac2352ed95e79645f4cdbd70ebf
Impact
Add 👍 to issues you consider important. If others are impacted by this issue, please ask them to add 👍 to it.
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
Reproduce the issue with a Lean file containing set_option internal.minimalSnapshots true, then delete the final e and inspect the VS Code Output area and panic messages. Trace the Lean server handling of this option change; done means the edit produces no observable behavior and no panic or error output.
Written by the indexing model from the issue text.
Assessment
- Domain
- compilers
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100