6 Commits

Include renames

Author	SHA1	Message	Date
jschoubben	3b989d8bb3	Callers of the pending assignments on the bucket: a replaced wait keeps its condition; one read of the key through assign (issue 1108) ... A wait that ended unmade and whose condition nobody answered is carried by the wait that replaces it, so the operator is never left without the condition for a module still not on its machine, and taking it back, its condition and the orphan sweep read it there. The condition id stays node.module.<id> with the string id. clearOrphaned says a taken-back wait too. TestAnAssignmentWaitingForItsBuildIsOneKeyOfTheAssignmentsBucket enters through the assign verb and reads the key before and after the build's outcome.	2026-10-18 05:19:32 +02:00
jschoubben	88ea361bf6	Fold a pending assignment into the value of its assignment key (issue 1094) ... A wait for a build is the value of <node>.<module> with state pending and a pending object (id p-<unix nanoseconds>, a string), so every reader that skips a value with a state skips it, and the controller's own lists skip it through Stands. The transitions are compare-and-set on the key's revision (claim, release, settle, repoint, mark); assigning over a wait carries it into the value that stands, applied when it was waiting; a plan pass never overwrites it; one open wait per machine and module, and a key that holds the module refuses a new one. The table is no longer read or written, ForgetEndedPending is gone (no key is removed), and a wait of a machine the store dropped is none. Callers change type only; their conditions are the next issue.	2026-10-18 05:17:30 +02:00
jochen	af63b233db	Leave out a module whose stored manifest has an unknown field, and raise it (hq ADR 0262 review) ... A key dropped silently ran a module without what its manifest says, and a key inside a block still failed the whole catalogue. Judge a key by what it is about, and narrow the listing to one machine.	2026-10-08 17:34:53 +02:00
jochen	8adb7f1a05	Give each pending assignment its own condition, and keep a raised row until it clears ... Second review of #150: one key per machine and module let a newer failure be cleared in the tick that raised it, pruning could orphan an open condition, and a build no longer waited for read as never asked although it may still run.	2026-10-08 16:45:43 +02:00
jochen	249d97d1c8	Make pending assignments safe to race, settle them on a tick, and say only what was checked ... Review of #150: a withdrawal could land between the look and the act, a failed ask read as a build in flight, a request kept the wrong asker, a build being registered read as not built, build "true" could ask a build nothing waited on, and a status read changed state. Claim a row under the machine's hold before making it, keep a request only once asked, settle on the controller's own tick, raise an assignment not made as a condition until it is answered, and tie each row to its machine.	2026-10-08 16:38:11 +02:00
jochen	7d63d2e68c	Say why assign finds no module, and keep an assignment pending on its build ... A merge asks for a new module's build, and assign answered "no module of that name" until the build registered it, which read as a module nobody registered (hq issue 325). Keep every build request, tell a build in flight, a module known and not built, and an unknown name apart, and make an assignment made while the build runs when the build registers the module.	2026-10-08 16:38:11 +02:00