Repository navigation
fix(qualification): detect hash-only rescue by tensor absence, not any file - #13
Conversation
…y file Hash-only rescue carries job.json and summary.json, so the "no file under published/" test sent real hash-only trees down the full-rescue branch and rejected them with qualification_artifact_custody_changed.
|
Warning Review limit reachedYou've used all free OSS reviews for now. Wait for the free limit to reset to keep reviewing this public repository. Next included review available in 43 minutes. View limit details
No actionable comments were generated in the recent review. 🎉 ℹ️ Recent review info
📝 Walkthrough
Merge Risk: ⚪ Minimal · up to
|
…t rescue ports, pinned miner host key - die when the frozen tree is missing instead of using /data/hypertrain-tree - refuse existing /data/hypertrain-h0/h1 before any spend (materialize would refuse an hour in) - h1 rescue base port 18600: 16 workers bind base..base+15, 18570 overlapped h0 - record launcher.pid: abort is TERM on it (setsid ignores INT/HUP) - default h1 miner ssh uses the admission-pinned known_hosts with StrictHostKeyChecking=yes
Hash-only rescue carries job.json and summary.json, so the "no file under
published/" test sent real hash-only trees down the full-rescue branch and
rejected them with qualification_artifact_custody_changed.
Summary by CodeRabbit