Design 47 H2: H-A-437, a cap is set above the live fill
This commit is contained in:
@@ -564,3 +564,9 @@ The lead's one-line answers to the questions H2's develop and review raise (impl
|
||||
delivery and every apply into a new builder state `consumers` (8 MiB), and the tool reads that state; "read when the
|
||||
health is asked" reads so (the bus is read at each event, no timer). The ledger's oldest-unacknowledged covers
|
||||
delivered messages only, as the runner's does. P3.
|
||||
- **H-A-437 (a cap is set above the live fill, 01:47)** H-A-411 (2). A state that names no cap gets `max-mib` 8 only when
|
||||
its live fill allows it: before writing a cap, the developer reads the bucket's fill with the bus module's `show`
|
||||
(the seat mesh-broker) on novox, and a state whose fill is above a quarter of 8 MiB gets the smallest power of two in
|
||||
MiB above four times its fill (the indexer's candidates, manifests, packages and seat-definitions are the ones to
|
||||
read); the cap chosen and the fill read are written in the commit. A cap below the live fill would refuse the owner's
|
||||
next write (P-failure-loud: a cap is a guard, never a cause). P-failure-loud, ADR 0595 §3.
|
||||
|
||||
Reference in New Issue
Block a user