Design 47 H: lead answer H-A-97 (a held take-in is kept in the indexer's state held) #768
@@ -410,3 +410,9 @@ Where two preparers disagreed, the chosen one is named.
|
||||
value `{pipeline}`, written by compare-and-set when a pipeline is placed and deleted at its end, its cancel or its
|
||||
approval wait; `pipelines-at-once` is judged against the `running.*` keys alone (a C-R3 field, the contracts' writer).
|
||||
P1, P3; H-A-60 holds (the runner reads only its queue keys).
|
||||
- **H-A-97 (indexer developer, 03:49)** A held take-in is kept in a small indexer state `held`, one key per branch
|
||||
`{branch, source, why, since}`, written when a `source-moved` is held and deleted at its take-in or skip (option c):
|
||||
`indexer_pending` reads it, and the watchman seeds from it (H-A-94). P4 (what the module holds is read, not derived
|
||||
from a scan of events), P3 (`since` is kept for the bound). The retired state `pending` was the pending revision of
|
||||
the manifest validation (ADR 0633 §1); this is not it. `indexer_take_in_pending` and `indexer_take_in_skip` are asks in
|
||||
the state `takeins`, the existing hand-act path. P7.
|
||||
|
||||
Reference in New Issue
Block a user