You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
verify-pyprocar: make fetched fixtures read-only at the OS level #288
Found by a reflect pass over the #277-#279 autopilot session.
The in-process audit-hook guard against writes into data/ took #264 plus #270 to cover dir_fd, symlink, link, chmod and utime, caused a CI failure without data/ and a false positive, and every agent brief still repeats the no-write ban by hand.
Suggested mechanism: verify.sh fetch runs chmod -R a-w on each fetched fixture, $H run works only on its reflink copy under data/verify-runs/, and a doctor check reports any writable fixture. The OS then refuses stray writes regardless of code path.
Fixed in dev by #303. verify.sh fetch now locks fetched fixtures read-only, run works on a writable copy, and doctor reports writable and unlockable fixtures. Every verify.sh command writes only strictly below the resolved data root; the documented worktree-own and cache writes are the exceptions. tests/test_fixture_copies.py bans raw fixture copies in tests. The verdicts (5 rounds) are on #303. The one-time lock for the shared data/ is in the PR body; run it from a checkout at merged dev.
Activity
test: copy fixtures with writable_copy so read-only fixtures work
test: copy fixtures with writable_copy so read-only fixtures work
refactor(verify-pyprocar): move the read-only fixture work to its own PR
test(verify-pyprocar): verify.sh changes nothing outside data/ under …
fix(verify-pyprocar): act only strictly below the main checkout's data/
docs(verify-pyprocar): state the data-root rule and name copies to un…
test(verify-pyprocar): verify.sh changes nothing outside data/ under …
fix(verify-pyprocar): act only strictly below the main checkout's data/
docs(verify-pyprocar): state the data-root rule and name copies to un…
test: assert the prefix download first and drop guard marks on tests …
test: download_from_hf leaves the shared Hugging Face cache alone
fix(download): fetch the one archive into a staging dir, not the shar…
refactor(verify-pyprocar): guard deletes like chmods and share the do…
test: take the hub arguments the fake ignores as keywords
4 remaining items
test: download_from_hf leaves the shared Hugging Face cache alone
fix(download): fetch the one archive into a staging dir, not the shar…
refactor(verify-pyprocar): guard deletes like chmods and share the do…
test: take the hub arguments the fake ignores as keywords
test(verify-pyprocar): verify.sh changes nothing outside data/ under …
fix(verify-pyprocar): act only strictly below the main checkout's data/
docs(verify-pyprocar): state the data-root rule and name copies to un…
test: assert the prefix download first and drop guard marks on tests …
test: download_from_hf leaves the shared Hugging Face cache alone
fix(download): fetch the one archive into a staging dir, not the shar…
refactor(verify-pyprocar): guard deletes like chmods and share the do…
test: take the hub arguments the fake ignores as keywords
feat(verify-pyprocar): make fetched fixtures read-only and keep verif…
lllangWV commentedon Oct 5, 2026
Fixed in dev by #303. verify.sh fetch now locks fetched fixtures read-only, run works on a writable copy, and doctor reports writable and unlockable fixtures. Every verify.sh command writes only strictly below the resolved data root; the documented worktree-own and cache writes are the exceptions. tests/test_fixture_copies.py bans raw fixture copies in tests. The verdicts (5 rounds) are on #303. The one-time lock for the shared data/ is in the PR body; run it from a checkout at merged dev.