Archived
The seat calls a gate that raised no machine the mesh composes an error, whatever judged it (hq issue 285) #106
Assignees
agent-ace
agent-g14
agent-novox
agent-shanks
jschoubben
mesh-tools
miel.truyen
nox-agent
Clear assignees
agent-ace
agent-g14
agent-novox
agent-shanks
jschoubben
mesh-tools
miel.truyen
nox-agent
No Assignees
No due date set.
Dependencies
No dependencies set.
Reference: novox/mesh-controller#106
Reference in New Issue
Block a user
After #104 merged, the re-checks of mesh-host#46 (build-1791331237244478582) and mesh-tools#19 (build-1791331238396298871) still said
gate PASS … (0 of 4 compose).Why: both checks were asked at 02:00:37–38 by the old controller process, the one replaced at 02:01:00. For a repository other than the controller, the judge is the controller the mesh runs, cloned beside the check at its registered build. At that moment that was
72d78024: #104's buildb39eaa48registered only with its plan at 02:00:53. The build log showsbeside it mesh-controller at 72d78024…judged by the controller the mesh runs. That judge predates the fix and the error rule, so it passed 0 of 4. The new process only reported the verdict.Fix: the judge being the running controller is the design, so the rule now also holds where the seat reads the verdict.
gateRaisedTheMeshreads the machines the verdict lists. A pass or warning in which any machine composes on the mesh (live-composes) and not in the gate's base is reported as error, whatever controller judged it.readGateVerdictalso reads a verdict that an older judge preceded with composition's own lines on stdout.It takes effect on the seat when build-agent is rebuilt from this. Until then, a judge at
b39eaa48or later already says error itself.Test:
TestTheSeatCallsAGateThatRaisedNoMachineAnError.Delivery
novox/mesh-controller@8b2abd08cdf8— delivered since 2026-10-07T00:44:23ZDelivery plan — builds build-agent, mesh-controller, route-proxy → ace, g14, novox, shanks; no bus step
Machines
Transitions
The commit's note under
refs/notes/mesh-plankeeps every transition:git log --notes=mesh-plan.Merge check at
858b4672mesh/merge-gate: PASS — every machine composes with the change as it did without (4 of 4 compose) (modules: build-agent, mesh-controller, route-proxy)mesh/repo-check: PASS — its merge-check.sh passedChange plan — builds build-agent, mesh-controller, route-proxy → ace, g14, novox, shanks; no bus step
Run by the build seat on ace as
build-1791331632898670475(builds --log build-1791331632898670475).Merge check at
8b2abd08mesh/merge-gate: PASS — every machine composes with the change as it did without (4 of 4 compose) (modules: build-agent, mesh-controller, route-proxy)mesh/repo-check: PASS — its merge-check.sh passedChange plan — builds build-agent, mesh-controller, route-proxy → ace, g14, novox, shanks; no bus step
Run by the build seat on g14 as
build-1791332299484999929(builds --log build-1791332299484999929).Second commit (
8b2abd0): the first check of #105 (build-1791331512096605198) ran on novox, and the build agent there was restarted mid-check by the rollout of #104. The ask was redelivered under the same id, collided with its own throwaway store (Conflict. The container name "/build-…-store" is already in use), and came back as gate ERROR, "the check could not run". A check now removes the containers an earlier delivery of the same id left before it raises its store. Test:TestARedeliveredCheckRemovesWhatItsEarlierDeliveryLeft. It passes withMESH_TEST_DOCKER=1against a local registry; it skips on the seat, which has no docker socket.Live: build-1791332299484999929 → PASS (4 of 4 compose), repository PASS.