mesh-catalog

Files

T

jschoubben 4254d17322

mesh/merge-gate pass: builds gitea, mesh-delivery → novox; no bus step; every machine composes with the change as it did without (4 of 4 compose)

Details

mesh/repo-check pass: its merge-check.sh passed, each part in its toolchain: merge-check.sh (go), merge-check-typescript.sh (typescript)

Details

mesh/delivery superseded: a newer head of the same pull request

Details

Say where a pending merge check is: queued since when, then building on which machine (hq issue 446)

The forge's holder set mesh/merge-gate pending as "the mesh is mapping this head onto its module graph" and nothing
changed it until the verdict, so a ten-minute controller check read as a stalled forge (issue 423). The holder now
says the head waits in the build queue since the local time it was announced; mesh-delivery follows the build
seat's started event and says the machine building it and since when, never over a verdict the forge holds.

2026-10-11 03:14:06 +02:00

announcing.test.ts

mesh-delivery: say a head whose merge check started and never answered (issue 438)

2026-10-11 02:16:34 +02:00

checks.test.ts

Cover a held merge only when the forge says a later delivered merge contains it (review of #150 )

2026-10-09 02:57:18 +02:00

delivery.test.ts

Put the merge check back to pending before a recheck asks it (hq issue 305)

2026-10-08 10:11:26 +02:00

guard.test.ts

gitea: a read-back that fails after the merge says the merge happened (review of issue 381)