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
parent 88ea361bf6
commit 3b989d8bb3
7 changed files with 204 additions and 37 deletions
@@ -160,3 +160,5 @@
 ./internal/inventory TestTwoClaimsOfOnePendingMakeOneAndTheOtherSeesFalse
 ./internal/inventory TestAssignOverAPendingKeepsItsRecordAsApplied
 ./internal/inventory TestAPendingIsMarkedOnceAndGoesWithItsMachine
+./internal/inventory TestAReplacedWaitNeverLeavesTheOperatorWithoutItsCondition
+./cmd/mesh-controller TestAnAssignmentWaitingForItsBuildIsOneKeyOfTheAssignmentsBucket