Files

T

jschoubben 0211844e6a

mesh/delivery delivering: 0 machine step(s) passed

Details

mesh/check pass 0211844e6ad3 on 0e985f9bf186 | unit 0 run 117 kept | int 0 run 119 kept | clone 5.4s | composition passed on 4 machines

Bound a state watch's hand-over by its progress, not its whole set, so a large state's newest keys are handed over (issue 1726)

The gitea module's watch of mesh-delivery-checker.owed failed at every attempt
since 03:05 on novox: about 200 owed keys, each a round trip to the bundle,
outlast a 10 s bound for the whole set. The bundle dropped its handler, the
oldest keys were written again every 40 s and the newest, handed over last,
never were: group fix/1937-done-key-blobs's pass never reached mesh/check.
StateWatch now fails only when no current value is handed over within
StateTimeout.

2026-10-24 07:42:08 +02:00

cmd/node-tools

Feature 57 (config and provisioning): release mesh-tools (the provider's StateBus, the SDK pin, templates), reviewed

2026-10-16 09:41:17 +00:00

internal

Bound a state watch's hand-over by its progress, not its whole set, so a large state's newest keys are handed over (issue 1726)

2026-10-24 07:42:08 +02:00

src

Say what becomes of an event a handler gives up on (hq issue 330)

2026-10-08 17:36:04 +02:00

test

node-tools: a tool call names its caller, and the module is told it from the subject (hq issue 365)

2026-10-11 05:19:08 +02:00

go.mod

Pin mesh-sdk at feat/r4g's head a2c813a6, its test fixture fix, with go.sum tidied

2026-10-23 17:06:12 +02:00

go.sum

Pin mesh-sdk at feat/r4g's head a2c813a6, its test fixture fix, with go.sum tidied

2026-10-23 17:06:12 +02:00

module.json

Wait on the gate's transition alone: today's module is forgotten (issue 1406)

2026-10-20 12:59:33 +00:00

package-lock.json

Bring node-tools' lock back in step with package.json, and fail the check when it falls behind (hq issue 624)

2026-10-13 15:12:10 +02:00

package.json

Give the TypeScript toolchain pg, mongodb and mssql, so a catalogue check can type-check the modules that use them (issue 385)

2026-10-12 12:27:46 +02:00

README.md

node-tools is a module beside mesh-tools: the runtime as a bundle, and serve is the console (hq ADR 0175, to-be 38 WP3)

2026-10-02 21:43:37 +02:00

tsconfig.json

node-tools is a module beside mesh-tools: the runtime as a bundle, and serve is the console (hq ADR 0175, to-be 38 WP3)

2026-10-02 21:43:37 +02:00

README.md

node-tools

The node's tool runtime as a module (novox/hq ADR 0175, to-be 38 WP3). Assigned to a machine, it is one process the host runs from this bundle, as the operator's account: it serves every assigned module's tools and every held seat's verbs on the bus, and answers MCP on the machine's loopback — the console (design 34). The controller composes the process (which bundles to load, where the credential is, whose machine it is); this manifest says only what the machine must have for it: the interpreter, a place for the credential, the loopback port, and leave to call every tool.

The code is the mesh-tools package in this directory; the module at the repository root, mesh-tools, builds the images TypeScript bundles are compiled in. See the repository README.