novox/mesh-catalog
13
0
Fork 0
Code Issues Pull Requests 5 Actions Packages Projects Releases Wiki Activity

Say where a pending merge check is: queued since when, then building on which machine (hq issue 446)
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

Browse Source 
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.
This commit is contained in:
jschoubben
2026-10-11 03:14:06 +02:00
parent ebd940fcd0
commit 4254d17322
9 changed files with 271 additions and 7 deletions
Download Patch File Download Diff File Expand all files Collapse all files
modules/mesh-delivery/module.json
+2 -1
View File
@@ -28,7 +28,8 @@
"gitea.pull.merged",
"gitea.pull.closed",
"mesh-controller.checked",
"mesh-controller.plan-moved"
"mesh-controller.plan-moved",
"node-build-agent.started"
],
"emits": [
"transition",