Repository navigation
mia-data: per-round harness source snapshots - #41
Merged
Merged
Conversation
…y pixi.lock alone Issue 54 was refused at production (PinMoved) because the harness checkout, which is also the working clone, had three commits since admission, even though the environment was identical. Now admission snapshots `harness/src` at the admitted commit into work_root/_harness/<commit>/ (read-only, flock, once per commit), and every job runs the pinned env's python on that snapshot through a `bin/harness` wrapper written into the workspace (PYTHONPATH ahead of the env's editable install). assert_pin compares only the pixi.lock digest. Co-Authored-By: Claude Fable 5.1 <noreply@anthropic.com>
krokicki
force-pushed
the
harness-snapshots
branch
from
October 13, 2026 01:04
aaaac19 to
76099f6
Compare
Co-Authored-By: Claude Fable 5.1 <noreply@anthropic.com>
Re-applies the per-round harness snapshot on the renamed, formatted code: harness_snapshot and the bin/harness wrapper in jobspec, the snapshot call in admit, harness_env in md check, and the jobspec tests. Co-Authored-By: Claude Fable 5.1 <noreply@anthropic.com>
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.
Issue mia-workflow-data#54 passed match, test crops and review, then was refused at production with
PinMoved: theharness.dircheckout is also the working clone, and it had three commits (API, CI, README; CLAUDE.md) between admission and approval. The environment was identical (pixi.lockdigest unchanged), only the source commit had moved. Spec §6 had a ponytail note anticipating this.Change
harness_snapshot(cfg, commit)extractsharness/srcat the admitted commit from the checkout intowork_root/_harness/<commit>/src, read-only, flock-serialised, once per commit, the same way snippets are snapshotted.admitcalls it, so the source is frozen the moment the pin is taken;_speccalls it too, idempotently.bin/harnesswrapper into the workspace and puts it first on PATH:PYTHONPATH=<snapshot>/src <env>/bin/python -P -c 'from mia_harness.cli import main; …'. PYTHONPATH precedes the env's editable install of the checkout's own source, verified against the real environment (imports resolve to the snapshot).-Pkeeps the job cwd offsys.path. The old commit from issue 54 snapshots fine too.assert_pincompares only thepixi.lockdigest. HEAD may move; a changed lock still refuses, since the env is shared.md checklooks for the env'spythoninstead of theharnessentry script.Not done: one environment per lock digest. Lock changes are rare and human, so they wait for in-flight rounds; the ponytail note in §6 now says that.
Tests: new cases for a HEAD move not touching an admitted round and for unknown commits; fixtures grew a
harness/src. 325 pass.🤖 Generated with Claude Code