Design 47 H: H-A-187, a pipeline's steps live one key per mover
This commit is contained in:
@@ -990,3 +990,12 @@ Where two preparers disagreed, the chosen one is named.
|
||||
modules declare the missing artifacts now, and the catalog's check refuses a manifest whose Go module imports a mesh
|
||||
package path that no module of the catalog declares as an artifact (the check reads go.mod requires against the
|
||||
declared artifacts). P3, P5, P7.
|
||||
- **H-A-187 (a pipeline's steps live one key per mover, 20:52)** Met at main.26 and main.30 (18:41): a pipeline
|
||||
record of 112 or 129 movers exceeded the bus's message limit once its steps were placed, and the runner could place
|
||||
nothing in it; raising the limit is not the shape (ADR 0486: large content goes by digest, never by a larger
|
||||
message; the SDK's message limit is 1 MiB). The runner's state keeps the pipeline record with its movers, tiers,
|
||||
call, source and outcome, and the steps of each mover under their own key, `steps.<pipeline>.<mover>`, written by
|
||||
compare-and-set as the record is; every read and judgement of steps (the end judgement, show, the step log, the
|
||||
hand acts rerun, accept, end-again) reads the mover keys; `show` answers a pipeline by its record and the mover keys
|
||||
it names, and takes an optional mover to answer one mover's steps alone (P4). A record never grows with the
|
||||
catalog. P1, P4, P7, ADR 0486.
|
||||
|
||||
Reference in New Issue
Block a user