Design 47 H: H-A-177, a restore point where no holder of the recovery seat is placed
This commit is contained in:
@@ -925,3 +925,12 @@ Where two preparers disagreed, the chosen one is named.
|
||||
never a step already asked; the why names only the edges whose two movers share a strongly connected group. The
|
||||
pipeline then ends by the end judgement of H-A-163: a required step not asked counts as not passed, so it ends
|
||||
failed as soon as no required step is still open, and steps already running run to their own end. P3, P7.
|
||||
- **H-A-177 (a restore point where no holder of the recovery seat is placed, 18:47)** Met at the indexer's
|
||||
take-in on the control-node (18:43): the node-engine asks the seat mesh-recovery for the module's restore point
|
||||
before it moves a data-holding module, and holds the take-in when nothing answers; the recovery module is placed
|
||||
nowhere, and this milestone says so ("the recovery module is not placed and is a later milestone's", H §456), so
|
||||
every data-holding module's take-in is held for good. The node-engine takes the restore point where the assigner's
|
||||
placements name a holder of mesh-recovery; where none is placed on the mesh, it moves the module without one and
|
||||
raises the finding `restore-point-missing` (warning, scope the machine, id the module) that clears at the next
|
||||
take-in with a point; it holds only where a holder is placed and does not answer (that is the holder's fault, said
|
||||
as today). P3 (loud, never a silent skip and never a silent hold), P7, H §456.
|
||||
|
||||
Reference in New Issue
Block a user