jschoubben
e5192f55ee
View: read no build record and no composition of the controller's: fingerprints against the builder's done keys alone, a move's judgement from the node agent's have (issue 1955, ADR 0571 §1, §6)
2026-10-29 23:08:46 +01:00
jschoubben
b01cf63237
Revert "Merge pull request 'Revert L3: its node-engine removed every held module on novox, the bus server among them (issue 774)' ( #109 ) from revert/774-l3 into main"
...
This reverts commit c1b4533201d8274204fb
2026-10-29 21:05:14 +01:00
jschoubben
6771db22ae
Revert L3 (mesh-delivery, merge d827420): its node-engine removed every held module on novox, the bus server among them, at 08:54 CET on 2026-10-29 (issue 774)
...
mesh/delivery merged: source.main moved to novox/mesh-delivery@c1b4533201c8
mesh/delivery-group group revert/774-l3 merged: every member is merged
mesh/check being carried to 6771db22ae69 on d8274204fbed | from mesh-catalog 1555241393fe | novox/mesh-delivery#109 in group revert/774-l3
L3 lands again with two fixes: a held module is never removed, and the grants cover L3's new subjects.
2026-10-29 09:42:29 +01:00
jschoubben
b2351a213d
Follow L2 under L3: the builder, checker, indexer and view read the seat mesh-placement's placement, the seat's Leased is the lease handed away, and the view keeps no read of the indexer's placement L2 removed (issue 774, ADR 0567 §8, ADR 0549 §3)
2026-10-28 21:54:47 +01:00
jschoubben
9a70d697af
The view shows a row per module the catalogue's placement puts on a node, and reads the controller's assignments no more (issue 774, ADR 0549 §3)
2026-10-28 21:54:47 +01:00
jschoubben
726bbf1f1f
The view writes a reach or says an event again when the bus refused it, so a refused write never leaves the reach state at an older have (issue 1126)
...
mesh/delivery merged: source.main moved to novox/mesh-delivery@2ac146078f47
mesh/check being carried to 726bbf1f1ffa on 2ac146078f47 | from e753009fbc71
The view remembered a reach value, a reached head and a motion event as written or said before the bus took them; a write refused at its start (no responders) was never made again while the derivation stayed the same, and mesh-delivery.show said mesh-delivery-view not running on shanks while node_haves said it running.
Quick fix: forget only the refused reach write. Thorough fix, chosen: every write and event the view makes after its lock (reach, reached head, delivered revision, motion) answers its error, and the model forgets what was refused, so the next change it takes in makes it again; one place, the writer of the state both mesh-delivery.show and knowledge-base.progress read.
2026-10-28 16:11:52 +01:00
jschoubben
96be0c3377
Move every delivery part's bus connection onto mesh-sdk's module helpers: credential, pinned dial, own-stream subjects, durable consumer, and refuse a hand-written one (issue 1242)
mesh/delivery merged: source.main moved to novox/mesh-delivery@24cb379434f5
mesh/delivery-group group fix/1242-bus-helper merged: every member is merged
mesh/check checking 96be0c3377c4 on c38e81c7f5e9 | novox/mesh-delivery#87 in group fix/1242-bus-helper
2026-10-27 20:40:49 +01:00
jschoubben
afd5a3ba07
A module a node wants and runs nothing countable of holds no head back; the reached head's event names its merges as not yet on the machines; pin mesh-sdk e44cbaf (review of issue 1280, ADR 0556 clause 2)
2026-10-26 21:15:31 +01:00
jschoubben
f907be2c14
The view derives per repository up to which merge every node runs it, keeps it as its state reach and says each reached head, so a fix on the machines reads delivered (issue 1280, ADR 0556 clauses 2 and 3)
2026-10-26 20:56:12 +01:00
jschoubben
da31740f00
The view's motion events carry the time they are about and call a held or past-bound module stopped, as the messenger reads them (issue 1906 D10)
2026-10-24 18:31:29 +02:00
jschoubben
a3815051cc
The view says modules in motion: moving, settled and stuck, once for a node, a module and a composition (issue 1906 D10, for the messenger)
2026-10-24 18:27:01 +02:00
jschoubben
86fd0bbe96
The view says its event delivered once for each source revision whose wants and haves are all there (issue 1906 D9, for issue 1946)
2026-10-24 16:47:09 +02:00
jschoubben
f947070b7b
The view shows the controller's judgement of the move beside each want (issue 1906 D7, ADR 0539 §14)
2026-10-24 16:38:24 +02:00
jschoubben
806c8bf0e4
Pin the assigner, watchman and view to mesh-sdk's release 6 head (issue 1943 S3) and give their test wants a composition digest
2026-10-24 16:32:09 +02:00
jschoubben
f048e2b443
The view shows each want beside the have of its node, and a source revision's derived state, in place of the comparison with sends (issue 1906 D7)
2026-10-24 16:23:51 +02:00
jschoubben
79ef768ea4
Show the backlog of build asks per language and kind: waiting, held by a node, and the oldest waiting ask's age (issue 1887 A8a)
2026-10-23 16:14:00 +02:00
jschoubben
57258b6fa4
Take the assigner's ask in the SDK's layout and name the asking in the view's answer, so a stale answer never fills a later asking (issue 1297 B9 and B10)
2026-10-23 15:22:32 +02:00
jschoubben
f7dd4ab586
Let the view answer the assigner's asks that need no proof, under the ask's view key, and refuse the merge's Approve on the phone's behalf (issue 1297 B9a)
2026-10-23 15:17:40 +02:00
jschoubben
57b0030258
Show every difference between the assigner's wants and the controller's sends with its rule, so the operator sees what holds a node back (issue 1297 B8)
2026-10-23 15:15:32 +02:00
jschoubben
9bd84941ee
Show a fingerprint of the new form against the builder's key of it, since the indexer no longer writes the old form and no build record names the new (issue 1851, I5)
...
The view watches the builder's builds; a value written before R4e keeps today's comparison. Pins mesh-sdk feat/r4e-sdk
9cb4d59.
2026-10-22 18:16:18 +02:00
mesh-tools
bf59b5a27b
An answer to an earlier asking no longer blocks the next asking: the teller and the view tell the asking by the answer's warrant id (review round 2, R2-1)
2026-10-20 01:35:26 +00:00
mesh-tools
34f585106f
Show the open asks in the delivery view: the gate's asks with no answer, in the table, the page and the command's JSON (issue 1345)
2026-10-20 00:34:28 +00:00
jschoubben
9e9c2a7a57
Show the candidate groups and each module's fingerprint against its trunk build's in the delivery view (issue 1241)
2026-10-19 15:10:16 +02:00
jschoubben
d309bb6cef
Put the view's socket in /var/lib/mesh-delivery-view-cli: the node-engine never places a module's directory below /run (issue 1134)
mesh/merge-gate head d309bb6cef45 merged into trunk 253f464a8155 — pass: builds mesh-delivery-view → shanks; no bus step; every machine composes with the c…
mesh/repo-check head d309bb6cef45 merged into trunk 253f464a8155 — pass: its merge-check.sh passed
2026-10-19 01:53:11 +02:00
jschoubben
954728b390
Show what the watchman says: offline presence, stuck keys and unreadable values, in the view and its command (issue 1168)
mesh/repo-check head 954728b39042 merged into trunk 8ae804fe6450 beside mesh-controller#388@ac79e293 — pass: its merge-check.sh passed
mesh/merge-gate head 954728b39042 merged into trunk 8ae804fe6450 — pass: group feat/delivery-watch composed: every machine composes with the change as it d…
mesh/delivery-group group feat/delivery-watch merged: every member is merged
2026-10-19 00:55:19 +02:00
jschoubben
eb8966c4b7
Add the mesh-delivery-view process, its manifest and the nox-delivery alias (issues 1134, 1137)
...
The process watches the three buckets on its own read-only credential; the manifest declares reads only, no state and no emits; the zsh item carries the alias as mesh-cli's does.
2026-10-18 19:31:50 +02:00
jschoubben
mesh-tools