51 Commits

Include renames

Author	SHA1	Message	Date
jschoubben	65496fc4f7	Merge main into feat/r4g-finish, keeping #37's same-branch mesh-sdk pin rule beside the node-engine check's controller placing (issue 1295)	2026-10-24 21:54:46 +02:00
jschoubben	991589fdd2	A try of a branch accepts a mesh-sdk pin at the head of mesh-sdk's branch of the same name, so a milestone's repositories can be tried before their pull requests (issue 1921)	2026-10-24 16:41:39 +02:00
jschoubben	840e56eddb	Fail the node-engine's check when the controller's trunk is unknown, so its step-nine test never skips (issue 1295)	2026-10-24 03:43:49 +02:00
jschoubben	45ab994777	Merge pull request 'The checker keeps a failed test's whole message with its cause first, and its status names the cause (issue 1901, with mesh-catalog)' (#30) from fix/1901-rebased into main ... Reviewed-on: #30	2026-10-23 22:36:03 +00:00
jschoubben	9261347a8f	Read a level's digest from mesh-sdk's list form, so kept verdicts hold for a check whose end names a package like token (issue 1930)	2026-10-23 23:37:49 +02:00
jschoubben	a697ee86d4	Test 1901/AC3: an older pair of build module and checker still agree (issue 1901)	2026-10-23 22:14:29 +02:00
jschoubben	0373a3b24e	mesh-delivery-checker: a failed test's verdict keeps its last lines and the status line names its error (issue 1901)	2026-10-23 22:13:41 +02:00
jschoubben	b2c545c40a	Place mesh-controller beside the node-engine's tests, which read its manifest (issue 1295, R4g)	2026-10-23 18:36:13 +02:00
jschoubben	ad26670996	Prove that a second check of the same heads keeps every package the first passed, the digest being taken inside the check ask as the build module answers it (issue 1917)	2026-10-23 17:18:37 +02:00
jschoubben	d3561923aa	Say the unit level's gofmt and go vet time in the check's line, and pin the group's mesh-sdk head that carries it (issue 1887 D7-go, review round 2 item 5)	2026-10-23 16:51:55 +02:00
jschoubben	52d8b9b753	Say in the checker's status that a check without a verdict waits in a build seat's stream, not behind a plan key or a capacity, as A5b left it (issue 1887, review round 2 item 4)	2026-10-23 16:47:20 +02:00
jschoubben	357e28f31d	Merge remote-tracking branch 'origin/feat/r4g' into feat/r4g ... # Conflicts: # modules/mesh-delivery-builder/internal/build/run_test.go	2026-10-23 16:46:05 +02:00
jschoubben	5ddc221833	Bound a build or check ask's step from its start, and drop the checker's whole-check bound, so asks waiting in the streams during a large rebuild are never failed and asked twice (issue 1887, review round 2 item 1; ADR 0525 §3, §6)	2026-10-23 16:45:35 +02:00
jschoubben	37860d46a0	Stop watching the node-engine's have in the checker: a check's asks wait in the build seats' streams, which redeliver a lost node's ask, so no check fails for want of a node; presence stays for an unheard forge and the assigner's presence (issue 1912)	2026-10-23 16:41:34 +02:00
jschoubben	527f87f94c	Merge branch 'feat/r4g-asks' into feat/r4g ... # Conflicts: # modules/mesh-delivery-checker/cmd/mesh-delivery-checker/judge.go # modules/mesh-delivery-checker/manifest_test.go # modules/mesh-delivery-checker/module.json	2026-10-23 16:20:17 +02:00
jschoubben	69577f739d	Judge hq as any repository, so its pull requests get a verdict and mesh/check from its Go tests and no script judges it (issue 1887 A10, ADR 0527 §2)	2026-10-23 16:11:43 +02:00
jschoubben	d9d1e57e3a	Delete the checker's hold, its own capacity and places, its node moves and its read of the controller's plans-building, so a check waits only in the build seats' streams (issue 1887 A5b, closes 1685; ADR 0525 §4, §7)	2026-10-23 16:09:34 +02:00
jschoubben	e4b639c6de	Judge each pull request's check as one ask on the build seats' check stream, a re-judge on recheck, so the checker chooses no node and a lost node's check is redelivered, not moved (issue 1887 A5a, ADR 0525 §1, §3, ADR 0536 §4)	2026-10-23 16:05:55 +02:00
jschoubben	7cbb1c4207	Wait for the assigner's composition only while the assigner is online, say at once that it is not judged when it is not, and take it in when the assigner writes it later, so no check waits its bound for a composition nobody makes (issue 1297, B3d)	2026-10-23 15:44:00 +02:00
jschoubben	4c98841d2a	Judge a repository the mesh knows no module of with both build modules, so mesh-lab's nested Go modules and its npm test both run (issue 1887 A12)	2026-10-23 15:41:57 +02:00
jschoubben	0f7091e4ac	Place the change's own repository beside it at its trunk, so a shrink-only list test compares with the trunk's copy at $MESH_CHECK_BESIDE/<name> (issue 1887 A12, ADR 0529 §2)	2026-10-23 15:35:37 +02:00
jschoubben	5091cab652	Read the assigner's composition into the checker's verdict in place of 'not yet run', failing a check whose composition failed, naming its machine (issue 1297, subtask B3d; ADR 0528 clause 5)	2026-10-23 15:27:59 +02:00
jschoubben	4ffe5f4d52	Start a never-judged head's check before the re-judges a trunk move asks, oldest first (issue 1897 S1) ... A new pull request waited 25 to 45 minutes behind every open pull request's re-judge after a merge. The semaphore becomes a ranked admission (ADR 0536 §4); checker_status names the waiting checks by kind.	2026-10-23 14:09:42 +02:00
jschoubben	2bdb8d0e00	Ask the Go build module to run the candidate when a merge changes it, and say in the line which program judged (issue 1898 K3) ... A change to mesh-build-go was judged by the installed module it replaces, so such pull requests were merged by hand. ADR 0535 §1, §2, §4, §5.	2026-10-23 14:06:57 +02:00
jschoubben	e762028760	Make checker_status count only steps that can still run, so a key a build module left running is not read as a full node (issue 1890) ... The checker's own places are released when a step ends or its wait passes the step bound; checker_status read every 'running' key in the build modules' steps buckets as a step in flight, so keys left by stopped, restarted or unassigned build modules looked like full nodes. It now lists them under left_running with why (past the bound, module not on the node, module not running), and leaves hq-only groups out of the unjudged candidates.	2026-10-23 09:03:45 +02:00
jschoubben	91e68ac13b	Merge feat/r4e-builder into feat/r4e (R4e integration) ... The checker's go.mod and go.sum conflicted on the mesh-sdk pin (checker lane 9cb4d59, builder lane e76a5a3): every module touched is pinned to the sdk lane's newest head d1af87a until the final SDK head.	2026-10-22 20:29:53 +02:00
jschoubben	cc63123b78	Carry each named path's object from a fetch's module trees into the merge preview, so the indexer narrows a candidate's tree as the merge's (issue 1758, I8, ADR 0499 §2) ... Pins mesh-sdk feat/r4e-sdk 9cb4d59.	2026-10-22 18:15:09 +02:00
jschoubben	7d740be255	Fail a check whose forge read reached nobody at the forge, and judge it again when the nodes change (issue 1624, C7) ... mesh-catalog #293 failed with 'go.mod cannot be read to check its mesh-sdk pin: nats: no responders', put at the build node, and stayed failed: the forge's tool runner was not answering for a moment, which is not the change's failure. The forge's reads now mark such a call unheard, as the build steps' calls are (issue 1820).	2026-10-22 18:07:22 +02:00
jschoubben	66ae4dc791	Format the judge (gofmt)	2026-10-22 18:06:11 +02:00
jschoubben	03eaf332ad	Say the composition's time and the machines it composed in a check's line, once the assigner reports them (issue 1300, C10) ... The line said only that the composition passed with an SDK commit, and its time sat among the parts that are dropped first, so a forge status never said how long the composition took or which machines it covered.	2026-10-22 18:06:07 +02:00
jschoubben	cbdcf6da0e	Give a group's TypeScript members the mesh-sdk member's package when its merge changes the package's paths, and pin the SDK's R4e head (ADR 0500 §4-§5, issue 1309's checker half) ... A TypeScript member of a group that changes mesh-sdk's package resolved the old version from the registry. Its Node fetch now names the mesh-sdk member's head, which the Node build module packs and serves, publishing nothing. The paths come from the indexer's modules value (lead decision L8), so a change of Go files or of the manifest alone resolves the registry as before. A test holds that no step of a check carries publish.	2026-10-22 18:05:12 +02:00
jschoubben	7abe230701	Judge a pushed head as a try on the checker, through checker_try and checker_try_read (ADR 0501 §5) ... mesh-controller's try asked build-agent, which leaves the checking at R4e. A try is now a key in the checker's state tries: the checker judges the head merged onto its trunk as it judges a pull request's head, through the same judge, places and holds, writes its end in the key and owes the forge nothing (no status, no preview, no verdict). One try per head, at most four at once; hq and a repository whose trunk the gate does not name are refused with "no level of <repo> is checked by the checker".	2026-10-22 18:03:28 +02:00
jschoubben	d9ace64681	Mark mesh/check pending on every open pull request into a moved trunk, and carry the gate's heads hash in each verdict (issue 1302's checker part, lead decision L4; issue 1300) ... The gate decides on mesh/check alone and matches an Approve's members by the heads hash over lowercase repositories and heads. A success judged on an old trunk stood on the forge while the next check waited for a place or a delivery, and a candidate whose repository the forge named in capitals carried a hash the gate never finds. A check that ends after its trunk moved now owes pending, not its verdict.	2026-10-22 17:58:49 +02:00
jschoubben	f7d8622deb	Keep a core repository's passing package under a digest that covers its siblings' commits, so core checks keep verdicts (issue 1287, C3a/C3b, lead decision L5) ... The checker took and kept nothing for a workspace given siblings, and every core repository has siblings, so the kept store stayed empty. The digest step now folds the siblings' commits in and echoes them; a verdict is kept or taken only when the echo equals the siblings the fetch was given, so a digest that misses one never poisons another check (ADR 0444, issue 482).	2026-10-22 17:56:59 +02:00
jschoubben	d83156fb21	Add checker_previews and checker_status read tools so the live acceptance of issues 1680 and 1685 can be read (C1, C2)	2026-10-22 17:25:11 +02:00
jschoubben	14c78e485f	Read a Go module's go.mod at the trunk when the head does not hold it, so a branch cut before the module was added passes the pin check (issue 1845)	2026-10-22 15:00:58 +02:00
jschoubben	bbb42d704c	The checker moves a step that no build node answers to another node and fails naming every node tried (issue 1820)	2026-10-22 10:04:29 +02:00
jschoubben	b519c8dde2	Keep nothing for a workspace given siblings, place the siblings where the tests state them, decide the hold from the listed plan keys (review D1-D3)	2026-10-21 21:52:41 +02:00
jschoubben	a20af30d54	A group's Go member naming a mesh-sdk commit that is neither on the trunk nor the group's head fails the check naming the member and the commit; a pin only a head carries names issue 1148 (issue 1624)	2026-10-21 21:34:35 +02:00
jschoubben	4cdba63b9b	Read tools for the checker's verdicts, a pull request's report and the kept verdicts (issue 1686)	2026-10-21 21:32:08 +02:00
jschoubben	fecabfca8b	Fit the status line in the forge's 140 characters by giving the times and counts in their compact form before dropping them (issue 1682)	2026-10-21 21:30:24 +02:00
jschoubben	4b063252e7	The checker's line says whether each candidate module's build is built, failed or waiting, read from the builder's keys (issue 1684)	2026-10-21 21:29:13 +02:00
jschoubben	7433b0d047	Start no check while a delivery builds: the checker reads the controller's bucket of the plans in their build phase, absent as empty (issue 1685)	2026-10-21 21:26:46 +02:00
jschoubben	a2a5167d72	Write a preview of the conflicts for a head that does not merge, and give the candidate's modules the reason; pin mesh-sdk to the R4c-5a head (issue 1445)	2026-10-21 21:25:45 +02:00
jschoubben	64599db3fa	Capture the fetch-with-base fixtures from mesh-catalog's code, and prove the checker whole against a real bus with fake build modules (issues 1679, 1287, 1288, 1289, 1678)	2026-10-21 21:23:22 +02:00
jschoubben	96ba6bd3dc	Say the verdict in a line of at most 140 characters and owe the status mesh/check in the checker's bucket, which the forge bridge performs once per revision; the checker's stream checks wakes the readers of its buckets (issues 1682, 1683)	2026-10-21 21:20:42 +02:00
jschoubben	4242fb5b0b	The indexer gives a candidate's touched module the fingerprint its merge preview gives it, and wakes on the checker's preview.written without a restart; pin mesh-sdk to the R4c-5a head (issues 1445, 1681)	2026-10-21 21:17:09 +02:00
jschoubben	e175343837	Write the merge preview of each head the checker fetched, for the indexer's fingerprints (issue 1680)	2026-10-21 21:12:48 +02:00
jschoubben	cfbd5b6d2d	Judge a head merged onto its trunk through the build modules: run only packages without a kept verdict, the change's own tests first, stop at the first failure (issues 1679, 1288, 1289)	2026-10-21 21:11:43 +02:00
jschoubben	27072a01b5	Add the checker module: it watches the candidates, claims a verdict once, owes the status mesh/check and ends a check past its bound (issue 1678)	2026-10-21 21:07:14 +02:00