mesh-delivery

Files

T

jschoubben 704fc8d467 The forge bridge reads a merge's module directories only where their tree changed (issue 1126)

mesh-catalog's 140 module directories are 420 forge reads per merge, past the 30 s bound
of a handled event while the forge is busy: the merged message of #535 timed out on every
try, and #3fb7951 needed seven (issue 1458 met the same kind at 131). A tree hash names its
bytes, so what was read at a tree is kept in the new state inputs and in memory, and a
merge reads only the directories it changed.

2026-10-28 11:10:09 +01:00

mesh-delivery-assigner

Grant the served keys of the trunk's manifest too, and pin mesh-sdk 7a8e9f9 in the assigner and mesh-grants on main's bus helpers (issue 1126, review round 1)

2026-10-27 21:13:41 +01:00

mesh-delivery-builder

Move every delivery part's bus connection onto mesh-sdk's module helpers: credential, pinned dial, own-stream subjects, durable consumer, and refuse a hand-written one (issue 1242)

2026-10-27 20:40:49 +01:00

mesh-delivery-checker

Checker: say loudly that a pull request cannot be judged when its repository has no trunk head (issue 1422)

2026-10-28 11:03:39 +01:00

mesh-delivery-forge-bridge

The forge bridge reads a merge's module directories only where their tree changed (issue 1126)