Files
mesh-catalog/modules/mesh-delivery-gate
jschoubben 758a8ad653 GT1: each owed act is a ledger entry of its own; every ledger write is measured
An act the gate owes the forge is now the entry act/<branch.source.act.id>
(type act, index acts on its record's key in the manifest), removed when
the forge bridge performed it; the head entry holds the record's fields
alone, and the record's acts are joined from their entries when read.
The record type keeps no act operation: a head written before this change
is read for its fields and the acts embedded in it are ignored (they are
notes and views of the few records in flight at the delivery; losing them
changes nothing the operator relies on). A view act's text is the record's
summary, the head's fields and a count of movers per outcome, so it fits
64 KiB for any record; gate_record still shows the whole record. The
64 KiB refusal measures every write, the head's, a mover's and an act's,
raising record-too-large, which the record's end clears for every entry
of it. The gate's whole test gains the step: 126 movers write 127 entries
plus their acts, none over 64 KiB, the head counting 126 and holding no
act; a take-in said again with a why past 64 KiB raises record-too-large
and the record's end clears it.

Builds: design 47 H2 §809, H-A-385, H-A-391, H-A-453 (3), H-A-455, H-A-457, H-A-459
2026-11-22 02:58:39 +01:00
..

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).

What it keeps (ADR 0539 §17)

The gate keeps the merge's states: proposed, ready, rejected, merged, held (a merge that reached the trunk without a passing check) and closed. It asks the operator's Approve and merges once, moving source.main. It asks the controller nothing, follows no plan event and derives nothing after the merge: whether a merged change reached the machines is the view's, from source.main, the wants and the haves. The seat mesh-delivery keeps the verbs deliveries, show, groups, checks, table, stalled (for a merge or a check past its bound), recheck and close; times, what-if, release, stop and retire-history went with the plans, so the gate stays a bundle serving the seat. A delivery an earlier owner kept in a state that is gone is read as the state it came to (merged, closed or proposed) when the gate starts.

When a refused or rejected merge is said (ADR 0505 §4, §5)

stalled is what the gate says to the operator as conditions, itself, on the operator-channel seat (ADR 0437 §9, issue 1275): after every look it raises each line, raises it again when its severity or need changes, and clears each that is listed no more; its bucket conditions keeps which it raised. (The controller's self-check that raised them went in release 6.) The gate's own list (show, deliveries) names every refusal and rejection at once, and the pull request is told at once; only stalled waits:

  • a merge refused because its trunk moved, whose check the gate asked again, is stalled only once that check answered and the merge was refused again, or twice the repository's last check time passed (at least the setting refusal-stall-floor-minutes, 10). Every other refusal is stalled at once.
  • a delivery that needs its author's new head (its check failed after its Approve: a conflict, a failed check, a rejected group) is stalled only once no new head came for the setting author-new-head-minutes (120). Its line says needs: new-head and names its author: the branch, and who opened the pull request as the forge's record says (the seat git's events). The ask names the issues linked to each pull request in the issue tracker (the seat issue-tracker's list); nothing is read from a description.

A merge the forge account cannot carry out is not asked (issue 1945)

Before the operator's Approve is asked, the gate reads through gitea_commit_statuses whether the forge's merging account writes each repository the ask covers (merge.writes). Where it does not, nothing is asked: the delivery waits on "the forge account cannot write : gitea_grant_write" (show), raised at once as a condition. The read holds until the gitea module's gitea.repo.writable (its grant, read back) or ten minutes, then the ask is made again; an approved merge of that repository the forge refused is asked again on the same event (writes.go).

The seat's hand-over

The gate took the seat mesh-delivery over from the module mesh-delivery (ADR 0449 §4, ADR 0450 §6, ADR 0454) and carried its deliveries, groups and pull keys once; the carry, and the reading of the controller's assignments and the node-engine's have keys that waited for it, went with release 6. catalogue_test.go keeps the catalogue to one claimant of the seat.