22 lines
1.3 KiB
Markdown
22 lines
1.3 KiB
Markdown
# mesh-delivery-gate
|
|
|
|
The `mesh-delivery-gate` module of the mesh catalogue: the gate of design 47. It claims the seat `mesh-delivery`, whose
|
|
name stays (ADR 0437 §11), and takes over from the module `mesh-delivery` (ADR 0437 §3, ADR 0450 §6). Its buckets are
|
|
`mesh-delivery-gate_*`.
|
|
|
|
## Files it does not know
|
|
|
|
Each directory or archive this module declares says how it treats a file it did not write (ADR 0422, ADR 0416).
|
|
|
|
- `${dir:state}`: everything in it is the program's; the mesh moves nothing out (ADR 0422 §2).
|
|
|
|
## A backup that failed before the send
|
|
|
|
The controller backs up the data of the modules a delivery moves before it asks or sends anything (ADR 0404). When its
|
|
walk's record, in `plan-moved`, names a backup that failed or stayed silent and nothing of the plan was sent, the
|
|
delivery goes from delivering to held (the observed row `backup failed`); the held reason names the machine, the
|
|
module and the backup's words, and the pull request's comment shows it. The hold does not lift by itself. `release`
|
|
of such a delivery asks the controller (`delivery-backups-again`) to take the backups again and the delivery goes on
|
|
delivering; a record from before the controller cleared the failure does not hold it again. A held delivery already
|
|
ends as covered or delivered when a later merge covers it.
|