leanprover-community / leanprover-community/repl

INTERNAL PANIC: Error when Pickling Proof State

Open
#81 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Dominant language
Lean
Stars
228
Forks
69
Avg merge
15m
Merged PRs (30d)
4

Description

When trying to pickle the proof state to test.olean, the system throws INTERNAL PANIC.

I've tried on versions v4.19.0-rc2, v4.18.0 and v4.10.0.

Steps to reproduce:

{"cmd": "import Mathlib", "env": null}

{"cmd": "theorem mathd_algebra_59 (b : ℝ) (h₀ : (4 : ℝ) ^ b + 2 ^ 3 = 12) : b = 1 := by sorry", "env": 0}

{"tactic": "have h₁ : 0 < 2 := by norm_num", "proofState": 0}

{"pickleTo": "test.olean", "proofState": 1}

Outputs:

{"env": 0}

{"sorries":
 [{"proofState": 0,
   "pos": {"line": 1, "column": 79},
   "goal": "b : ℝ\nh₀ : 4 ^ b + 2 ^ 3 = 12\n⊢ b = 1",
   "endPos": {"line": 1, "column": 84}}],
 "messages":
 [{"severity": "warning",
   "pos": {"line": 1, "column": 8},
   "endPos": {"line": 1, "column": 24},
   "data": "declaration uses 'sorry'"}],
 "env": 1}

{"proofState": 1,
 "goals": ["b : ℝ\nh₀ : 4 ^ b + 2 ^ 3 = 12\nh₁ : 0 < 2\n⊢ b = 1"]}

INTERNAL PANIC: closures cannot be compacted. One possible cause of this error is trying to store a function in a persistent environment extension.

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start by running the reported JSON sequence against the REPL and confirm that the final {"pickleTo":"test.olean","proofState":1} command produces the panic. Trace the proof-state pickling path and the persistent environment extension involved, then verify that the same sequence completes without the INTERNAL PANIC and writes test.olean.

Written by the indexing model from the issue text.

Assessment

Domain
tooling
Issue type
Bug
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
35/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.