mesh-tools
41f18b2452
mesh/merge-gate waits for its group's composed check
mesh/repo-check head 41f18b24527f merged into trunk a3a9b8749d12 beside mesh-tools#37@06e6721e — fail: its merge-check.sh failed: --- FAIL: TestTheGateCarr…
mesh/delivery-group group feat/r3e-the-gate rejected: a member's own check failed
mesh/delivery superseded: a newer head of the same pull request
20 lines
1.1 KiB
Markdown
20 lines
1.1 KiB
Markdown
# mesh-delivery
|
|
|
|
The `mesh-delivery` module of the mesh catalogue: claims the seat `mesh-delivery`.
|
|
|
|
## 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.
|