Design 47 H: H-A-283, a re-pin of the same source keeps a mover in its pipeline; its build is asked again there
This commit is contained in:
@@ -1618,3 +1618,13 @@ Where two preparers disagreed, the chosen one is named.
|
||||
and are given again (every outstanding message redelivered), handled twice. The hub pulls at most twenty messages
|
||||
per pull and sends in-progress for a handler that runs past a third of the consumer's ack wait, so no buffered
|
||||
message is redelivered for waiting in the client. In the SDK (the event hub), for every module. P4, P7.
|
||||
- **H-A-283 (a re-pin of the same source keeps a mover in its pipeline; its build is asked again there, 17:35)** Met
|
||||
live: a module importing twenty packages released by its own pipeline is re-pinned at each of their publishes
|
||||
(H-A-204), each re-pin keeps a revision of the same source, each revision's pipeline takes the module out of the
|
||||
running one (H-A-223), and each newer build withdraws the older before it publishes: the tool runner's release ran
|
||||
from 0.1.41 to 0.1.48 in nine minutes and never published. A re-pin revision of the SAME source revision moves no
|
||||
mover out of a running or waiting pipeline: the pipeline keeps the mover, writes its new fingerprint and pins, and
|
||||
asks its build again (the builder's take-over of the series is that build); the re-pin revision starts no pipeline
|
||||
of its own for such movers. Only a revision of a new source (a merge) moves movers. Until the indexer re-pins once
|
||||
per release (owed, H2: pins from the reservation, confirmed at publish), this holds the pipeline steady. In the
|
||||
runner. ADR 0682 (one take-in, one pipeline), P7.
|
||||
|
||||
Reference in New Issue
Block a user