Development record
A drain's in-progress lane is renewed only when its own step or receipt runs, so if the host pauses the lane for more than the two-hour default lease another account takes the reservation over five minutes after expiry and works the same issue; the land fence runs only at arming, after the push and the pull request, so the duplicate becomes a public pull request.
issueresolvedmajoriss-2610161015393523
A drain's in-progress lane is renewed only when its own step or receipt runs, so if the host pauses the lane for more than the two-hour default lease another account takes the reservation over five minutes after expiry and works the same issue; the land fence runs only at arming, after the push and the pull request, so the duplicate becomes a public pull request.
Frontmatter
| id | iss-2610161015393523 |
|---|---|
| type | issue |
| lifecycle | resolved |
| severity | major |
.abcd/work/issues/resolved/iss-2610161015393523-a-drain-s-in-progress-lane-is-renewed.md
open on GitHub ↗ · commit history ↗
References1
- itd-2610161016394967Drains on several accounts share the workrelated
mentions4
- dcn-26101610403743432026-10-16 — A drain renews its lane's lease every move (facilitator-on-delegation, drain-many-accounts): every drain move, waiting or not, renews its in-progress lane's reservation at half its lease before its window gate, independent of the lane's progress; and the land stage checks the reservation before its push as well as at arming, handing the lane back at once when the hold is now another's, so a lapsed lease never becomes a duplicate pull request (grounds: lease keep-alives as Chubby and etcd keep them, and fencing before a write; iss-2610161015393523).
- dcn-26101700284050292026-10-17 — The landing's push fence renews with the tip's own term, and a lane it stops on another person's hold is handed back as stuck (facilitator-on-delegation, drain-many-accounts): the check before the push is the land fence's own act, a fetch and a live renewal of this person's reservation from this copy, made for every run that holds a reservation, an intent's included, since a duplicate pull request is as wrong there; it renews with the tip's own term (renewalTerm) rather than the fence's day, so the push neither cuts nor stretches the lease the arming later sets; its refusals are the fence's, contention, worded for the push; a hold now another person's, or released as finished on origin's default branch, is a refusal that cannot change, so the drain hands the lane back at once through the stuck lane's route, kind stuck, with no new hand-back kind; and the drain's renewal of the lane in progress reads the move's own view, renews only a lane not parked at land (the merged-lane finish renews those), and names a renewal that failed or found the hold another's in the move's next step (grounds: lease keep-alives as Chubby and etcd keep them, fencing before a write, and one canonical primitive for the stuck route; spc-2610161044461448 step 7; iss-2610161015393523)
- itd-2609091034175565Before an agent starts on an item, it reserves it on the shared remote, and everyone who works on the project sees the reservation
- spc-2610161044461448drain-many-accounts