Development record
The host judgement is asked before the issue's reservation is checked, and an issue another account holds is retried on every move with a full check (plan, sibling worktree scan, fetch), so several drains all judge and retry the same head of the queue, since every drain takes the same order (category, severity, oldest).
issueresolvedmajoriss-2610161015387318
The host judgement is asked before the issue's reservation is checked, and an issue another account holds is retried on every move with a full check (plan, sibling worktree scan, fetch), so several drains all judge and retry the same head of the queue, since every drain takes the same order (category, severity, oldest).
Frontmatter
| id | iss-2610161015387318 |
|---|---|
| type | issue |
| lifecycle | resolved |
| severity | major |
.abcd/work/issues/resolved/iss-2610161015387318-the-host-judgement-is-asked-before-the.md
open on GitHub ↗ · commit history ↗
References1
- itd-2610161016394967Drains on several accounts share the workrelated
mentions2
- dcn-26101610403688902026-10-16 — A drain reserves an issue before it judges it (facilitator-on-delegation, drain-many-accounts): the drain reserves an issue before it asks any judgement over it, so the reservation push is the compare-and-swap that keeps two accounts from judging or promoting one issue; an issue or footprint another copy holds in the move's view is passed over with no push and no judgement; and within each group of one category and severity the drain takes file-scoped issues first and orders each part by a rendezvous hash of the holder, the copy key and the issue id, so accounts and copies spread across the group with no coordinator (grounds: competing consumers with skip-locked selection, and rendezvous hashing; iss-2610161015387318).
- spc-2610161044461448drain-many-accounts