Design 47 H2: H-A-424, I4's four points
This commit is contained in:
@@ -460,3 +460,13 @@ The lead's one-line answers to the questions H2's develop and review raise (impl
|
||||
- **H-A-423 (a paged read's total, 01:23)** §811. A read that pages by the bus's cursor cannot count what it has not
|
||||
read, so `total` is given when one page holds the whole read and left out otherwise; `capped` says the cut. A reader
|
||||
wanting the count reads to the end. P-failure-loud (no number that is not counted).
|
||||
- **H-A-424 (I4's four points, 01:19)** §805. (1) A kept catalog revision is written once, so pins are not added to one:
|
||||
the indexer gathers a pipeline's version-reserved events for one event revision and writes one re-pin revision when
|
||||
the gathering settles, that is at the first pipeline-started or step-ended of that pipeline it hears after the
|
||||
reservations (the builder reserves every mover before it asks the first build), or at its own `reserved-settle` bound,
|
||||
a new setting of the indexer (default 30 s); H-A-420 (1)'s "add their pins" reads so. (2) The key-ttl of
|
||||
`reserved.<revision>.<module>` is a new indexer setting `reserved-keep`, default 24 h (a pipeline lives at most
|
||||
hours; a key outliving its pipeline costs nothing but bytes). (3) The re-pin at a reservation runs on the branch of the
|
||||
event's revision only: a reservation belongs to one pipeline of one branch; a release re-pins every watched branch
|
||||
as today. (4) Yes: releasedPins takes the series' numbered when it is newer than the newest, as acceptedSeries does,
|
||||
so the release's package-published moves no fingerprint. P3, P-NATS-native.
|
||||
|
||||
Reference in New Issue
Block a user