Skip to content

Use the reference environment's uv.lock#2

Open
maxsloef-goodfire wants to merge 5 commits into
mainfrom
use-reference-lock
Open

Use the reference environment's uv.lock#2
maxsloef-goodfire wants to merge 5 commits into
mainfrom
use-reference-lock

Conversation

@maxsloef-goodfire

Copy link
Copy Markdown

Follow-up to #1, which you merged before my second commit landed on the branch (fast review! 🏃): this swaps in the uv.lock from your validated environment (sha256 22cb1f78…, uv 0.11.16) in place of my fresh resolution. Same direct pins; 16 transitive patch-level versions differ. Verified: venv rebuilt from this lock, vllm/lm_eval/torch import and run evals.

🤖 Generated with Claude Code

Codex and others added 5 commits June 8, 2026 21:51
The midtraining repo's prepare_olmes_venv.sh runs `uv sync --group gpu
--frozen` in this checkout, but uv.lock was gitignored and never
committed, so the lockfile only existed in the original author's
working copy and every fresh clone failed with "Unable to find
lockfile at uv.lock".

Track uv.lock (resolved 2026-06-11 against the pinned pyproject:
lm_eval==0.4.3, vllm==0.11.0, torch 2.8.0+cu128) and drop it from
.gitignore so the eval environment is reproducible from a clean
bootstrap.

Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
Commit uv.lock so prepare_olmes_venv.sh works on fresh clones
Replace the freshly-resolved lockfile with the one from the validated
eval environment (sha256 22cb1f78..., uv 0.11.16). The two differed
only in 16 transitive patch-level versions; all direct pins
(lm_eval==0.4.3, vllm==0.11.0, torch 2.8.0+cu128) are identical.

Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants