Development record
2026-10-29 — iss-2610261837062463: a lapsed revival narrows its own-copy overlap check to the lanes' changed files only once no lane is still at or before its implement stage and no spec step is pending; otherwise it judges the whole footprint and backs off, because an implementer's uncommitted edits are invisible on the branch tip and two automated lanes must never edit one file. The waiter and implement status also leave a run parked at land alone, as the drain does, and re-read the reservation view under the run lock so one lapse is renewed once.
decisiondcn-2610291925508286
2026-10-29 — iss-2610261837062463: a lapsed revival narrows its own-copy overlap check to the lanes' changed files only once no lane is still at or before its implement stage and no spec step is pending; otherwise it judges the whole footprint and backs off, because an implementer's uncommitted edits are invisible on the branch tip and two automated lanes must never edit one file. The waiter and implement status also leave a run parked at land alone, as the drain does, and re-read the reservation view under the run lock so one lapse is renewed once.
Frontmatter
| id | dcn-2610291925508286 |
|---|---|
| type | decision |
| date | 2026-10-29 |
.abcd/work/decisions/dcn-2610291925508286-iss-2610261837062463-a-lapsed-revival.md
open on GitHub ↗ · commit history ↗
mentions1
- iss-2610261837062463A build's reservation lapses while the host waits on an agent, because only implement step renews it (renewReservation in internal/core/implement/loop/reservation.go): build itd-82's run-2610260500113538 reserved itd-82 until 07:00Z, its implementer then held the implement stage for about thirteen hours under the shared machine's load gate, and no step ran to renew it. Revived after the lapse, the reservation is judged like a new one (crowd.go), and a build's automated act backs off on any overlap with the same person's other copy, so the renewal was refused for loop.go, in the footprint of iss-2610142134353345, live from the main checkout. The run goes on to validation holding no reservation, and the land fence will stop it, though nothing of the other record's work touches the lane's files.