leanprover / leanprover/lean4

Lake build clean build with artifact cache leads to "missing data file"

Open
#14,435 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

bug P-medium
Dominant language
Lean
Stars
9.2k
Forks
990
Avg merge
1d 17h
Merged PRs (30d)
175

Description

Prerequisites
Steps to Reproduce

Start with:

lake +nightly-2026-07-17 new test lib
cd test
export LAKE_ARTIFACT_CACHE=true
lake cache clean # just to be sure

Add the following dependency to lakefile.toml:

[[require]]
name = "verso"
git = "https://github.com/leanprover/verso"
rev = "nightly-testing"

Then:

echo "import VersoManual.InlineLean" > Test.lean
lake build
lake clean
lake build

Finally open .lake/packages/verso/src/verso-manual/VersoManual/InlineLean.lean in VSCode. That leads to "missing data file for module MultiVerso.Manifest".

Versions

Output of #version or #eval Lean.versionString:

Lean 4.34.0, commit 79bec6d064d8672cb10864cad3d9fd054b6917ae
Target: x86_64-unknown-linux-gnu`

OS version, if not using live.lean-lang.org: Arch Linux.

Additional Information

Happens at least with v4.33.0-rc1, too.

Contributor guide

Open the contributing guide

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 reproducing the commands in the issue with Lean 4.34.0 and LAKE_ARTIFACT_CACHE=true, then compare the first build, lake clean, and second build. Inspect the generated artifact data for VersoManual.InlineLean.lean and the reported MultiVerso.Manifest module. Done means a clean rebuild completes and VSCode opens the file without a missing data file error.

Written by the indexing model from the issue text.

Assessment

Domain
build-system
Issue type
Bug
Difficulty
4/5
Estimated time
3-5 days
Activity status
Quiet
Clarity
Mostly clear
Newbie friendliness
48/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.