mesh-lab

Files

T

jochen c7c7268db0

mesh/merge-gate head c7c7268db08c merged into trunk d3ef6fa44caf — pass: the change touches no module of the mesh's graph (run 2)

Details

mesh/repo-check head c7c7268db08c merged into trunk d3ef6fa44caf — pass: its merge-check.sh passed, each part in its toolchain: merge-check.sh (typescript)…

Details

mesh/delivery delivered

Details

Raise genesis past its broker step and hold that the bus is kept (hq issue 590, ADR 0333 §5)

The bed runs the installer from bare twice: first with a catalogue missing the nats module, so it stops
at the broker step by name and the bed reads the bus there; then with the whole catalogue, through the
step. It passes only when exactly one bus container runs, it is mesh-broker-nats on the module's image,
every stream that held something before the step is still the same stream, and the mesh still hears
from the first node. A first run that never reaches the step skips with the reason; a second run that
stops at the step fails.

The judgement is a pure function, test/integration/bus-kept.ts, held by unit tests without a lab.

2026-10-13 02:13:35 +02:00

integration

Raise genesis past its broker step and hold that the bus is kept (hq issue 590, ADR 0333 §5)

2026-10-13 02:13:35 +02:00

beds-read-the-catalogue.test.ts

A cache consumer presents the login it was granted, checked over the catalogue; the two-node bed's baserow keeps its own cache and the bed asserts it answers (issue 081)

2026-09-22 12:26:34 +02:00

bus-kept.test.ts

Raise genesis past its broker step and hold that the bus is kept (hq issue 590, ADR 0333 §5)

2026-10-13 02:13:35 +02:00

cache-consumers-present-their-login.test.ts

Review of 081: the bed asserts baserow chose its own cache and it challenges for its password; the check reads only what a module hands its software; stale comments