After G: tests against the composed bus, kept events heard or loud, one way of asking work #626

Merged
mesh-tools merged 1 commits from design/47-G-after-list-2 into main 2026-11-16 12:01:14 +00:00
@@ -109,3 +109,38 @@ deals with it, which is how the list is kept true.
- The node-engine's repository holds about 1721 unit tests against the budget of 500.
- The live indexer was seen refusing the assigner's manifest for claiming `mesh-placement`, which neither main nor
G's branch claims: confirm the verdict after G's take-in.
## Tests run against what runs (the operator, 2026-11-16 about 13:00 CET)
- **A test runs against the bus as the mesh composes it.** The pipeline runner's integration test made its own
shared event stream catching every seat event, so a step's end reached the runner there; on the live bus a step's
end is a kept event on a stream of its own, which the runner never bound, and no pipeline could pass (fixed in the
runner at G's start, 2026-11-16). Wanted: a principle ("a test runs against what the module runs against: the bus as
the mesh composes it from the manifest, never a layout written in the test"); the shared library gives an
integration test the streams, kept streams and consumers the composition makes for the module's manifest; every
integration test that creates its own streams moves onto it (count them first); the runner's test publishes a step's
end on the kept stream.
- **A handler of a kept event is heard or fails loudly.** Starting a program's events binds only the shared stream;
kept seat events need a second call, and a program that registers a handler for one and never makes it hears
nothing and says nothing. The shared library binds the kept streams of every registered handler itself, or refuses
to start.
## One way of asking work (2026-11-16)
- The builder, the pipeline runner, the indexer (its validation before a take-in) and the checker each ask the build
seats in a shape of their own; the validation rides the check queue behind pipeline steps (a 6-second validation
waited over 20 minutes). Parked by the operator for research right after G: one generic pipeline for work and gates.
- An ask given again after a fix keeps its old form (a step asked with no module directory came back without one).
- The builder asks a failing build again every two to three minutes, reserving a new version each time.
- The builder's queue tool lists only the oldest 50 waiting entries (left over from 2026-11-14), so it cannot show
what waits now.
- The pipeline runner serves no tools on the control-node and logs nothing per step; the build seat's step events say
no pipeline before a step ends; `mesh_wait` refuses the build seats' and the runner's events; the bus's stream reader
cuts a body at 4 KiB; a running test step logs nothing.
- `TestTheBuildModulesKeepNoCopyOfTheDeliverySDKsStepCode` fails on mesh-catalog's main (the empty
`modules/mesh-build-go/buildstep` directory); the seven `checks/` tests, nats-tools and distribution fail in a run over
the whole of mesh-catalog.
- The glossary's **pipeline** and **pipeline step** entries leave out the build, which the runner asks as the step
`build` of the seat `mesh-builds`: correct them.
- A pipeline the runner set aside before A-446 with steps already written (`main.940.mesh-delivery-sdk`) is started
again by neither of the runner's start paths.