fix(lab): transport-relaunch dirs disambiguate on timestamp collision
Two concurrent cells dying to TLS resets in the same second both mint the same 1-second timestamp relaunch dir; the loser threw "refusing to reuse" and the run was lost (hit 2-for-2 on banking at 8-worker concurrency). A relaunched run now bumps a -2/-3 suffix until a fresh dir frees up. Operator-pinned runs keep the strict refuse-to-reuse guard. Co-Authored-By: Claude <noreply@anthropic.com>
| Repository | eliziff/Beaver |
|---|---|
| Author | Eli Ziff <eliasziff@gmail.com> |
| Authored | |
| Parents | 9ccf6da5 |
| Stats | 1 file changed , +28 , -3 |
| Part of | Evaluation harness: Beaver-CAN and LegalBench-RAG adapters |
Capture this commit into my fork
Download a Markdown prompt that tells Claude how to port this
exact commit into your working tree. Run it via
claude -p < capture-commit-5072329e.md
from inside the repo you want the change in.