Commit Graph
1252 Commits
Author SHA1 Message Date
jschoubben c5f76cb974 composer: a build that can never be made is blamed, not a reason to judge no machine (G-24 H3)
A module awaited on a machine whose revision gives it no fingerprint (the case's none) is held as its
node-engine holds it, the machine judged from that composition, and the module blamed with the revision's
none words, so only its own pipelines fail. An awaited build with a fingerprint keeps the machine not judged.

Builds: design 47 G §721, §722, A-470j, A-470k
2026-11-17 12:04:20 +01:00
jschoubben 8700aabba3 composer: a machine that fails with no module held is searched for its culprit, bounded by blame_tries (G-24 H2)
The composer program has no settings, so the assigner bounds the search through the request: only the candidate's
changed modules placed on the machine are held, one at a time, the search ending at the first whose hold ends the
problem; past the bound the untried are named. A request with no blame_tries gets no search.

Builds: design 47 G §721, §733; A-468h, A-468i, A-469i, A-469j, A-469k
2026-11-17 11:21:49 +01:00
jschoubben 06781d4dbc composer: a machine's verdict names the modules it blames (G-24 H1)
The assigner fails only the composition steps of the modules a machine blames, so the composer names them: the modules
the change refuses that the node held neither in its read nor composing without the change, answered structured by
ComposeSent, and both owners of a path two modules own, from the resolution's pairs. Blamed is always written, so a
verdict blaming none is told from an old composer's. The two request-file tests are one, for the test budget.

Builds: design 47 G §721, §733; A-468h, A-468l, A-469h, A-469j
2026-11-17 11:19:54 +01:00
mesh-tools d0b208b668 Merge pull request 'node-engine: the golden node grant holds every verb the manifest invokes (A-461c)' (#234) from fix/47-G-node-engine-integration into main 2026-11-17 08:49:22 +00:00
jschoubben 85ad1eef74 nodegrant: the A-461c check of the golden grant runs in an existing test, no test added (test budget)
Builds: design 47 G-22 A-461c
2026-11-17 09:46:55 +01:00
jschoubben 51b89964c5 nodegrant: the golden grant is checked against the manifest's invokes and holds every invoked verb's call subject (A-461c)
Builds: design 47 G-22 A-461c, A-461b
2026-11-17 09:41:36 +01:00
jschoubben 1a6a380507 nodegrant: the node's grant holds the catalog verb module the composer asks (A-461b)
The composer asks the trunk build of another node's module through the seat mesh-catalog's verb module (declared in the manifest); the golden grant lacked its call subject, so the ask hung to the node's bound in every pass and held the integration tests.

Builds: design 47 G-22 A-461b
2026-11-17 09:39:03 +01:00
mesh-tools 0612916af0 Merge pull request 'Node-engine: holds carry their wait; upstream images are no part; the store's address from another node's placed or trunk build (A-453, A-454, A-454a, A-461, A-461a, A-461b)' (#233) from fix/47-G-hold-carries-its-wait into main 2026-11-17 00:23:00 +00:00
jschoubben 10a6824abe Compose: a fault of finding the store other than its listen refusal still refuses the node, tested (A-461b)
Builds: design 47 G A-461b
2026-11-17 01:22:03 +01:00
jschoubben bb285f9c1b Selfcompose, compose: the trunk build stands where a placement names none; the fallback is another node's only; only the store listen refusal holds fetchers (A-461b)
Builds: design 47 G A-461b
2026-11-17 01:19:21 +01:00
jschoubben cbed32524a Selfcompose: another node's module whose running build has no entry is laid from its placed build's entry (A-461, A-461a)
Builds: design 47 G A-461 (first sentence), A-461a
2026-11-17 01:12:37 +01:00
jschoubben b132653fc0 Compose: an artifact store with no known address holds the modules that fetch from it, not the node (A-461, second part)
Builds: design 47 G A-461 (second sentence; the first, laying another node's module from its want's entry, waits on a lead answer)
2026-11-17 01:10:49 +01:00
jschoubben 523ad97e28 Node-engine: a digest the want's parts name always counts as fetched (A-454a)
Builds: design 47 G A-454a
2026-11-17 01:06:57 +01:00
jschoubben 5b4484efd8 Node-engine: a hold after an interrupted backup waits as the others do (A-453)
Builds: design 47 G A-453 (§541)
2026-11-17 01:00:57 +01:00
jschoubben 0a43489a74 Node-engine: an upstream copy served through the registry seat is no part of a want (A-454)
Builds: design 47 G A-454
2026-11-17 00:49:44 +01:00
jschoubben dbb77efab1 Node-engine: only an image the mesh built is a part of a want (A-454)
A container's image counts as fetched for the parts check only when the composition
names the seat it came through; an upstream image its manifest pins by digest is no
part and is never 'fetched and not in the want's parts'.

Builds: design 47 G A-454 (§421's parts check, A-432)
2026-11-17 00:48:46 +01:00
jschoubben 1b9f9355b5 Node-engine: a hold of the composition carries its wait, step compose (A-453)
A module not composed for want of its entry (entry-asked, entry-missing) and a want
whose parts differ write their have with a Wait of step compose and that reason, as
the kept data's holds do; the hold for a failed backup carries none.

Builds: design 47 G A-453 (ADR 0539 §16, §541)
2026-11-17 00:39:39 +01:00
mesh-tools 72385fd84a Merge pull request 'Node-engine: an unanswered requirement costs its consumer, not the machine (A-452)' (#232) from fix/47-G-unanswered-requirement-holds-consumer into main 2026-11-16 23:28:45 +00:00
jschoubben 3bb895152f Resolution: an optional consumer of an unanswered requirement is left absent and listed (A-452, ADR 0330 §3, §7)
Builds: design 47 G A-452
2026-11-17 00:27:47 +01:00
jschoubben c6d893e141 Resolution: a requirement nothing in the mesh answers holds its consumers too; optional ones stay absent (A-452)
The mesh-wide refusal ("nothing in this mesh provides") holds its consumers as the
node-wide one does; a module that wants the name only optionally is left absent
(ADR 0330 §3), never held. A held why still names the nodes that offer nothing
here. The two tests of the first commit are folded as rows into one table test
that replaces two existing ones.

Builds: design 47 G A-452
2026-11-17 00:25:30 +01:00
jschoubben 310ff0cabc Resolution: an unanswered requirement holds its consumers, not the node (A-452)
A requirement nothing answers no longer refuses the whole composition: each
module that wants it is held with the "nothing provides" words, as a refused
claim's claimant is, and the node composes the rest. Held modules stay in the
set, so what they provide still counts. The node is refused when every module
is held or no module of the set wants the name. Tests that used an unanswered
requirement to make a node's own set fail now use an ambiguous one.

Builds: design 47 G A-452 (extends A-405, A-407; ADR 0636 §3)
2026-11-17 00:18:25 +01:00
mesh-tools 13fcfae051 Merge pull request 'Node-engine: judge a move's data forms from the entry kept of the running build; no endless handing again' (#231) from fix/47-G-engine-own-manifest into main 2026-11-16 19:00:07 +00:00
jschoubben f8f33e54a7 Node-engine: judge a move's data forms from the entry kept of the running build; no endless handing again
The running build's entry stays held (kept in the composition state) while the node runs it, though the catalog half dropped it; the agent no longer tells the composer it waits for a composition it holds, and the composer hands again when the entry answers.

Builds: design 47 G §296, §297, A-113, §614
2026-11-16 19:59:20 +01:00
mesh-tools 869d15e6d3 Merge pull request 'Design 47 G start: node-engine fixes placed by hand (A-226b/c, A-237b/c, manifest digest)' (#230) from fix/47-G-start-2-host into main 2026-11-16 14:15:10 +00:00
jschoubben 292aa54bbb node-engine: compose-candidate's chunked input is tested through HandActs.Call and past the inline bound, folded into the compose integration test; comments cite A-237c
Builds: design 47 G (G-22 lead answers 2) A-237c; A-237b
2026-11-16 14:49:39 +01:00
jschoubben f539cdb7ec node-engine: compose-candidate sends its composition input in chunks over the link's connection when asked with a call token (A-237b)
Builds: design 47 G (G-22 lead answers 2) A-237b; A-237, A-249
2026-11-16 14:38:31 +01:00
jschoubben 3b365ba7cc node-engine: a catalog revision's manifest digest is made the candidate's hex form (A-226b)
Builds: design 47 G (G-22 lead answers 2) A-226b
2026-11-16 14:26:03 +01:00
jschoubben 6eb41a17e1 node-engine: a run's compose-candidate key reads candidates.run-<id> by its group, with no heads compared (A-226c)
Builds: design 47 G (G-22 lead answers 2) A-226c; A-226b
2026-11-16 14:00:30 +01:00
jschoubben a1cd4a1a2f node-engine: compose-candidate reads a branch pipeline's catalog revision through mesh-catalog.revision and composes it as the candidate (A-226b)
Builds: design 47 G (G-22 lead answers 2) A-226b; ADR 0593 §7
2026-11-16 13:58:36 +01:00
jschoubben 7a30c0d54c node-engine: fold the three new tests into existing tests as cases, so the branch adds no test function (test budget)
Builds: design 47 G §524, §525, A-405, A-407, A-430, A-430a, A-432 (hq main 3723b2ea), ADR 0259 §8
2026-11-16 09:40:29 +01:00
jschoubben a9eb4372d9 Merge remote-tracking branch 'origin/main' into fix/47-G-start-2-host 2026-11-16 09:25:14 +01:00
jschoubben c025bb5f1e node-engine: at a start a hold for differing parts or a missing entry is judged again, not kept as a failed backup waiting for an answer (§524, §421, ADR 0568 §4) 2026-11-16 01:04:07 +01:00
jschoubben 5a3510b115 node-engine: a runtime of its own runs the tool runner's program, which the module's parts check leaves out (design 47 G §524, A-432) 2026-11-16 01:01:01 +01:00
jschoubben 7f892a757c node-engine: a held tool runner's kept program is not replaced by the tools bundles it serves, so novox's new indexer is run by it (ADR 0259 §8) 2026-11-16 00:50:33 +01:00
jschoubben 40ed0633e0 node-engine: a held tool runner keeps its running program, so a module of its own account is not held for want of a runtime that runs (ADR 0259 §8) 2026-11-16 00:34:50 +01:00
jschoubben 5bbde5db40 node-engine: the composer judges a changed want by its fingerprint, version, parts and keeping node, so a want that gains its parts is composed (design 47 G §525) 2026-11-16 00:28:41 +01:00
mesh-tools 21e452df28 Merge pull request 'Node-engine invokes the registries' versions verbs (design 47 G A-430a)' (#229) from fix/47-G-engine-invokes-versions into main 2026-11-15 16:08:13 +00:00
jschoubben dc32afdd7e Node-engine invokes the registries' versions verbs, so its grant admits resolving a want's version (design 47 G A-430a)
The grants part admits a seat verb's invokers by the manifest on the trunk; a node-engine that resolves a want's
version through oci-artifact-registry.versions and container-image-registry.versions is refused on the bus until
its manifest on main names both. Manifest only: a node-engine that does not resolve versions never calls them.
2026-11-15 17:04:37 +01:00
jschoubben 8a0c39280d Node-engine: a want naming its version is resolved to its digests through the registry seats (A-430a)
A want of a released build names the module's version and no parts. Each artifact of the build's entry is
resolved at that version through the verb versions of its kind's registry seat: oci-artifact-registry for a
bundle or an archive, container-image-registry for an image, under <module>/<artifact> or a package's own
name. An upstream copy, which is not numbered, takes the digest its manifest pins. partsMissing, buildOf and
KeptBuildOf (and the shadow's added modules) read those digests; a want with parts is read as before.

A lookup that fails is said in the journal, naming the module, the version and the seat, and holds the module
whole: nothing of it is composed. It is asked again after a minute. The manifest invokes both verbs.

Builds: design 47 G A-430, A-430a; lead answer A-430b
2026-11-15 16:52:59 +01:00
jschoubben a00cccfe0d Node-engine: a running module the assignment names is held, never removed, whatever composed nothing of it (A-410)
Builds: design 47 G A-410
2026-11-14 23:38:29 +01:00
jschoubben 592b4002bd Node-engine: a running module with no fingerprint is held in its answer, never removed (A-410)
Builds: design 47 G A-410
2026-11-14 23:18:36 +01:00
jschoubben 0adc5ab4e6 Node-engine: a running module without an entry resolves as the newest build its want names
Builds: design 47 G §421, lead answers A-405 and A-407
2026-11-14 22:47:33 +01:00
jschoubben 6079f634d6 Node-engine: say whether its seat is served and how long the first looks of what runs and of the accounts take (A-405)
Live on novox 2026-11-14 root-free answered 'judged no account yet' minutes after the start and nothing was logged:
the seat's serving and the first looks were silent.
2026-11-14 15:59:28 +01:00
jschoubben eaf011e971 Node-engine: a first start whose composing never ends is named by MESH_ENGINE_OWN_MODULE (A-404, live start recovery)
A-403 named the engine from the base's catalogue, but on novox the base stops at the first manifest it cannot read,
before mesh-host, so the engine stayed unnamed and its seat unserved.
2026-11-14 15:53:44 +01:00
jschoubben 1c3b2597ba Node-engine: named from the catalogue the base read, before the rest of the input (A-403)
Live on novox 2026-11-14 the G node-engine never ended a composing pass, so it never named its own module and never
served its seat node-engine: grants got no responders for root-free, judged novox not free, and the operator channel
held every Approve ask (the seed, hq#609) as no channel could prove who answered.
2026-11-14 15:48:45 +01:00
mesh-tools fd023f7473 Merge pull request 'Milestone 47 G: mesh-host's part of the one release' (#228) from feat/47-G-join12 into main 2026-11-13 13:09:29 +00:00
jschoubben 5caa760f5e A-342 engine-node-env: every process runs with its node's name as MESH_NODE
mesh/delivery merged: source.main moved to novox/mesh-host@fd023f7473bc
mesh/delivery-group group feat/47-G-join12 merged: every member is merged
mesh/check failed (2): mesh-delivery-checker: no published of the tagged version of go-meshconditions of me…; and 1 more | 5caa760f5eaa on fd023f7473bc
The apply gives each process the declaration's For as MESH_NODE beside its own env, so a process that reads MESH_NODE (mesh-sdk, the zfs follower's writer and its node-service-manager calls) names its node.

Builds: design 47 G A-342

Claude-Session: https://claude.ai/code/session_01NcbgfGKaxw984XyAPfLm4h
2026-11-13 09:20:46 +01:00
jschoubben d63aae1d55 Merge main into feat/47-G-join11: the node-engine's if-config, config-lines, config-json and stop at a failure (issue 1979)
The whole test's web manifest keeps G's entry form (no build artifact, the entry read by fingerprint) and takes main's resources under if-config and config-lines.

Builds: design 47 G §421; design 42 zfs-owns-zfs H1-H5

Claude-Session: https://claude.ai/code/session_01NcbgfGKaxw984XyAPfLm4h
2026-11-13 09:10:44 +01:00
mesh-tools f8acfaeed7 Merge pull request 'The node-engine stops a module's apply at its first failed resource, and reads if-config, config-lines and config-json (issue 1979)' (#227) from feature/1979-zfs-owns-zfs into main 2026-11-13 08:00:43 +00:00
jschoubben 0a9d1efe89 Merge main into feat/47-G-join11 (G takes in main before its push)
mesh/delivery-group group feat/47-G-join11 checking: 17 of 17 member(s) ready
mesh/delivery closed: a newer head of the same pull request
mesh/check checking 0a9d1efe8918 on f8acfaeed79d | novox/mesh-host#226 in group feat/47-G-join11
Claude-Session: https://claude.ai/code/session_01NcbgfGKaxw984XyAPfLm4h
2026-11-13 02:16:56 +01:00