5 Commits

Include renames

Author	SHA1	Message	Date
jschoubben	a0c971cea9	Make a module's consumer from now and refuse a start word in consumes, so no part replays a week at its first start (issue 1279, ADR 0443)	2026-10-19 21:53:08 +02:00
jschoubben	14fe2ad736	Split the unit level from the integration level outside cmd, builder, link, catalogue, inventory; merge-check.sh times and bounds the unit level (issue 895)	2026-10-17 20:41:57 +02:00
jochen	be92762969	Give every test a bus of its own, at the release the mesh runs (hq ADR 0237) ... The live tests reached one shared bus and assert, read and remove the mesh's own objects by their fixed names, so packages run in parallel deleted what each other read and the suite passed only one package at a time; a red suite read as noise. internal/testbus starts a server per test, linked in at the nats-server release go.mod pins, and a test holds that pin to the catalogue's bus image and to the facts snapshot's bus when there is one, so the tests never run a bus the mesh does not. The waiter test read a timing (the most connections held at one look) and now reads the state it means (the fewest held across the wait). make check runs the packages in parallel under the race detector, with a timeout.	2026-10-06 21:17:02 +02:00
jochen	5761737687	Name the issue the event consumer fix answers: 248	2026-10-05 17:15:49 +02:00
jochen	89ec48b9a9	Make the controller's event consumer from now, and give a stuck one a reset ... A consumer made with the server's default replays everything a stream that keeps history holds: the controller's EVENTS consumer, re-made that way, replayed a week of merges and builds one at a time and held every new one behind them. FromNow makes it start at the end; broker consumer-reset re-makes a stuck one from now, refusing a work queue. hq issue 244.	2026-10-05 17:15:25 +02:00