5 Commits

Include renames

Author	SHA1	Message	Date
jochen	424a7eec82	Keep what discovery heard when a round hears nothing, and fetch only changed announcements (issue 554) ... A round in which no PING reached the laptop's console within the 750 ms window was taken as the mesh's answer that nothing is there, and replaced the index: every seat and module call was refused for five seconds at a time. Discovery now waits up to its patience for a first PING, a round that heard nothing is not kept, a runtime not heard this round is resolved from what it announced last (said with its age), and a round that misses runtimes is logged once. A PING carries a digest of what the instance serves, so an unchanged announcement is not pulled again every round (some 880 kB to the laptop).	2026-10-12 13:56:50 +02:00
jochen	379d19d907	Wait for every runtime discovery hears from, and name the ones it misses ... The console gathered $SRV.INFO answers for a fixed 750 ms. The laptop's runtime (48 modules, 341 endpoints, 164 kB) answers last every time: its answer crosses to the broker on another machine and back, a median of 365 ms on a quiet link and 813 ms in one of 25 rounds measured. When it missed the window the console said its modules ran nowhere ("nothing in the mesh is called slack") or only on another machine. Discovery now asks $SRV.PING alongside $SRV.INFO and waits, past the window and up to 5 s, for every instance that answered PING. A runtime that never sends what it serves, or answered before and not now, is named in every answer that might concern it instead of the module being called missing. An answer still too large after first-line descriptions drops them, and says so in its metadata. mesh_runtimes reports, per runtime, its machine, how long its answer took, its size, its modules and tools, whether it was shortened and when it was last heard, and the runtimes and machines not heard.	2026-10-05 15:36:10 +02:00
jochen	b3ebdd5edd	Keep a machine's discovery answer under the bus's message limit ... Every tool's schema in one $SRV.INFO reply outgrew max_payload on machines serving 137-206 tools, and the refused reply was dropped silently, so search and a machine's view went empty. Module tools now announce without schema; describe and tools/list ask the module for it. An answer still too large has its descriptions cut to a line, and a failed reply is logged.	2026-10-04 17:06:20 +02:00
jochen	f11ac6441c	Announce only on the subjects the grants allow (hq ADR 0197) ... Both runtimes subscribed $SRV.<verb>.> as a wildcard; the grants allow the bare question and the service's own name and instance. The bus refused the wildcard, and the TypeScript runtime treats a refused subscription as fatal, so every per-module container crash-looped after the image rolled. They now subscribe exactly $SRV.<verb>, $SRV.<verb>.<name> and $SRV.<verb>.<name>.<id>.	2026-10-03 22:31:02 +02:00
jochen	7722668220	Every runtime announces what it serves in the NATS services protocol; the console discovers by asking the bus (hq ADR 0197) ... The Go runtime answers $SRV.PING, $SRV.INFO and $SRV.STATS (and per name and id) in the io.nats.micro.v1 format with what it serves at the moment it is asked: one service per runtime process, since the bus admits one reply per request from each responder, and one endpoint per tool per subject, its metadata saying module, seat, scope, machine, description, schema and whether the module is interchangeable. Serving is unchanged. The console gathers one $SRV.INFO request's answers instead of asking the catalogue's roster and each module's tools, and reads the controller's records as JSON for what should have answered: an assignment with tools that did not announce is named, a module without tools never is. The text parsers of node list and module list are gone. Packages share the test bus: go test -p 1.	2026-10-03 22:14:16 +02:00