Repository navigation
Conversation
- Point downstream projects at lake exe cache get - Document LAKE_ARTIFACT_CACHE for local reuse - Leave lake cache put as a later, credentialed step
cdbattags
requested review from
SamuelSchlesinger,
arademaker,
chenson2018,
crei,
fmontesi and
sorrachai
as code owners
October 5, 2026 20:40
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
The "Using CSLib in your project" section (#206) stops at
lake update cslib. The nextlake buildthen compiles Mathlib. This addslake exe cache getthere, which is the same step Mathlib documents for downstream projects.lake exe cache getdoes not keep CSLib's own build products. The README also notesLAKE_ARTIFACT_CACHE=trueso another checkout of the same toolchain can reuse a local build, andLAKE_RESTORE_ARTIFACTS=truewhen a tool expects files under.lake/build.lake cache putis only described, not added to CI: it needsLAKE_CACHE_KEYand a cache service (LAKE_CACHE_SERVICE, orLAKE_CACHE_ARTIFACT_ENDPOINTwithLAKE_CACHE_REVISION_ENDPOINT).Drafted with Grok 4.7, the 500k-context high-effort setting, in Cursor. I used it to read
LAKE_ARTIFACT_CACHE,LAKE_RESTORE_ARTIFACTS, andLAKE_CACHE_KEYin Lean 4.35 (Lake.Config.Env,PackageConfig.enableArtifactCache) and to write the README paragraph. This repository has noLLM-generatedlabel; the disclosure above is the step CONTRIBUTING.md asks for, via the Mathlib policy.