8 Commits

Include renames

Author	SHA1	Message	Date
jschoubben	790d1c82d0	A follower joining a watched state hears its current values, and a templates archive is fetched once ... A read could start a state's watch before its follower joined, and a change landing in that gap woke nothing (review of ADR 0580 §2): a joining follower now runs over the copy's current values before any later change. The watched reader keeps each archive once per URL, and both caches are bounded. Claude-Session: https://claude.ai/code/session_01NcbgfJ9Gum47zkFKWRaovL	2026-11-01 09:53:17 +01:00
jschoubben	db4eb3bbf4	One watched copy of the states a module reads, and the composer's reader over it ... A whole state read key by key took the provisioner's composition of one node past 30 s and the assigner's compare past its call bound (ADR 0580 clause 1): each state is now one watch's current values, kept by its changes; a build is read by key and a manifest once per digest. Claude-Session: https://claude.ai/code/session_01NcbgfJ9Gum47zkFKWRaovL	2026-11-01 09:53:17 +01:00
jschoubben	1dc5d8cb3d	Run a watch's handler beside the runtime, and give a refused watch up loudly (issue 774) ... The provisioner's watches of gitea.bound, mesh-vault.bound and postgres.bound failed every minute for an hour on the control-node ("the current values ... did not arrive in 10s") and 1257 changes were refused as "names no watch of this bundle". Both sides were at fault. The SDK answered a change only once its handler returned, so a slow handler (Rejudge waits on the lock its composition holds) counted against the runtime's 10 s bound on the current values; and when the runtime gave up, the SDK forgot the id at once. The runtime (mesh-tools node-tools internal/bus/state.go StateWatch) stops its watcher on that bound but still drains and delivers the values already buffered, to an id nobody holds. Quick fix: a longer runtime bound. Thorough fix here: each state and provision watch has a follower that takes a change in order and answers at once, its handler on its own goroutine; Watch still returns only once the current values were handled, and a handler's error is said on standard error. A watch the runtime refuses is said given up and kept by id, so a change still handed to it is refused saying so. KeptState.Follow asks again with backoff until taken, the loop four modules wrote for themselves. A log watch keeps its answer after the handler: that is its back-pressure.	2026-10-30 18:15:51 +01:00
jschoubben	7b02f63daf	Refuse a key-value write too large for its bucket before it is put (issue 774) ... mesh-grants' sealed grants and the controller's merge record each met "message size exceeds maximum" (JetStream 10054) only after the put, and a writer that retries looped on a value that can never land; an update over the limit was even answered as a revision mismatch, which every compare-and-set writer retries. Quick fix: cap the two values in their modules. Thorough fix, chosen because the kind was met twice and every module writes through the SDK: the package kvlimit checks a value against its bucket's largest message (read from its stream and kept) before the put, naming the bucket, the key, the size and the limit, and turns the bus's own refusal into the same *TooLarge (errors.Is kvlimit.ErrTooLarge), so no writer retries it. The SDK's own writers use it: process.State (Put, Create, CreateTTL, Update), process.AwaitedBucket, the runtime state of a bundle (stdio KeptState, against the module state's 256 KiB) and mesh-hand-compose. A value that can outgrow its bucket is split over keys or kept in the object store with its name in the key.	2026-10-30 18:02:18 +01:00
jschoubben	bc6c8a6d24	Let a bundle write a key with its own time to live and hear its expiry, so pulses, settles and bounds expire on the bus through the runtime (issue 1952)	2026-10-29 22:14:42 +01:00
jochen	a75add0d59	Module state is hq ADR 0201 after all: the derived-value record moved to 0202 on hq main	2026-10-04 11:02:45 +02:00
jochen	d937c7bc2f	Module state is hq ADR 0202: 0201 landed first for a provider's derivations	2026-10-04 03:44:56 +02:00
jochen	096c5562a4	A module's state through the runtime, in TypeScript and Go (novox/hq ADR 0201) ... state(name) / stdio.State(name): get, put, delete, keys and watch over the runtime's mesh/state verbs. A watch's handler is registered under the id it is asked with, so its current values — which arrive before the watch is answered — and its changes reach it and no other watch.	2026-10-04 02:47:31 +02:00