fix(restore-drill): chown extracted scratch tree so fsck actually runs #5507
ccantynzAI Reviewcommented 12d ago
AI Triage
(no summary)
Priority: medium Risk area: mixed
Suggested labels: (no label suggestions) Suggested reviewers: (no reviewer suggestions)
Suggestions only — nothing has been applied. The PR author stays in control.
gluecron[bot]🤖 botAI Reviewcommented 12d ago
AI review unavailable
The platform's AI balance is exhausted, so AI generation is temporarily unavailable. Nothing was lost. You can queue this as a repair for the internal agent from the repository's Health page, or try again once the balance is restored. The PR is otherwise unchanged.
Cross-repo impact
See what breaks downstream if this PR merges.
⮌ Merged
This pull request was merged into main.
c comment · e edit title · m merge · a approve · r request changes · ? shortcuts
What broke
The first offsite-sourced drill (2026-08-20, after wiring
EnvironmentFileinto the drill unit) "failed" all 48 repos — but not one fsck ever ran. Root extracting the tarball restores the archived container UIDs, and git refuses repos owned by another UID (detected dubious ownership). The DB half passed cleanly from the offsite copy (pull_requestsdrift 1 within tolerance 353 — the Aug-16 false alarm is gone).Fix
chown -Rthe scratch extraction tree to the drill user aftertar -xzf(no-op when tar already extracted as us;|| trueso a partial chown can't change the verdict on its own).git -c safe.directory='*'on the fsck call.bash -nclean. The spawn-based test harness can't run on the Windows dev box (nobashin Bun's PATH — the known runner-sandbox exclusion); the merge-gate CI runs it for real.This is the last red gate before the cutover runbook's Phase 1 is provably green from the offsite copy.
🤖 Generated with Claude Code