1935 Commits

Include renames

Author	SHA1	Message	Date
jschoubben	8943a290f5	Merge remote-tracking branch 'origin/main' into feat/try-speed	2026-10-25 01:29:43 +02:00
jschoubben	537e2ef31f	mesh-build-go: check with CGO_ENABLED=0 as production builds do, and let the lint's go vet, a compile alone, warm the shared cache for later checks (issue 1921, try speed S11)	2026-10-25 01:29:21 +02:00
jschoubben	545a172bbf	mesh-build-go: bound the processes of an ask's levels together, the processors divided by the build capacity, through lock files in its workspace, now that the levels run side by side (issue 1921, try speed S10)	2026-10-25 01:26:50 +02:00
jschoubben	391095ccb9	mesh-build-go: run in the integration level only the tests its tags add, read from the source, so the unit tests are not run twice (issue 1921, try speed S7)	2026-10-25 01:13:21 +02:00
jschoubben	8536021f82	mesh-build-go: bring the mirror to the trunk commit so the merge preview deepens from it, and place the siblings side by side (issue 1921, try speed S6)	2026-10-25 01:10:19 +02:00
jschoubben	23307935b9	mesh-build-go: start the integration level's store and bus beside its compile, and compile the go.mod directories side by side without running a test binary (issue 1921, try speed S5)	2026-10-25 01:06:53 +02:00
jschoubben	d5d6fd7412	mesh-build-go: run a unit level's lint beside its tests under one bound, so its wall time is the longer of the two; a lint failure still fails the level (issue 1921, try speed S4)	2026-10-25 01:04:35 +02:00
jschoubben	2e69099354	mesh-build-go: lint only the packages a unit level runs, in one vet pass with every tag unless a tag leaves a file out, so a small change's lint costs a few packages (issue 1921, try speed S3)	2026-10-25 01:02:08 +02:00
jschoubben	5c65b1f3dc	mesh-build-go: give each ask a cache layer in its workspace, so what its vet compiles its unit tests and integration level find compiled (issue 1921, try speed S2)	2026-10-25 01:00:32 +02:00
jschoubben	4f074e87c7	mesh-build-go: say how long each phase of a fetch ran, so a check's "clone" time splits into mirror, fetch, preview, repack, siblings and modules (issue 1921, try speed S1)	2026-10-25 00:54:55 +02:00
jschoubben	ac6712cbb5	Pin mesh-sdk to feat/r6 748c564, which carries main's composer (issue 1943)	2026-10-25 00:02:45 +02:00
jschoubben	1968aba6e0	mesh-build-go, mesh-build-node: run every package of a check's level after a failure (issue 1921) ... Pins mesh-sdk fix/1921-every-failure, whose check ask no longer stops a level at its first failing test step, so one check runs every package and names every failure. A captured fixture with a failing test in each of two packages proves the build module's test step names both.	2026-10-24 23:47:27 +02:00
jschoubben	5b32342ac2	Merge main into feat/r6: keep R6's gate, which already carries #474's catch-up at start, and drop the seat and walk adoption R6 removed ... The reads-outside markers, mesh-build-go's compose job and gitea's forge-account fix come in from main.	2026-10-24 23:03:42 +02:00
jschoubben	6fb0ceeef8	Merge pull request 'R4g finish: mesh-build-go's compose job, the reads-outside marker in the digest, merge-check.sh gone (issues 1295, 1621-1623, 1935)' (#473) from feat/r4g-finish into main ... Reviewed-on: #473	2026-10-24 20:56:49 +00:00
mesh-tools	c651161787	Merge pull request 'gitea's forge-account reads the forge's own host key file before scanning its sshd, so a forge restart no longer refuses every forge account (issue 1939)' (#472) from fix/1939-forge-host-key into main	2026-10-24 20:05:39 +00:00
jschoubben	b67b5af5e6	Pin the gate to mesh-sdk feat/r6 at d7a9b968 (issue 1946)	2026-10-24 21:18:26 +02:00
jschoubben	d700ceca20	Pin the gate to mesh-sdk feat/r6 at 7f9cc0e5 (issue 1946)	2026-10-24 20:43:41 +02:00
jschoubben	3a1017f559	Pin the gate to mesh-sdk feat/r6 at e45bdc08 (issue 1946)	2026-10-24 20:22:07 +02:00
jschoubben	a17d0c8e93	The messenger holds and tells what the delivery view says is in motion, not the controller's plans (issue 1946)	2026-10-24 18:25:38 +02:00
jschoubben	9fa6710296	Pin the gate to mesh-sdk feat/r6 at a523a8cb (issue 1946)	2026-10-24 18:18:06 +02:00
jschoubben	05f849979c	Match a fix to a delivered revision by what the gate says of its merge; keep #474's source catch-up at start (issues 1946, 1726)	2026-10-24 18:13:40 +02:00
jschoubben	4dee77df23	Pin the gate to the head of mesh-sdk feat/r6 (issue 1946)	2026-10-24 17:54:30 +02:00
jschoubben	8a79877a15	A newer delivered revision covers the older merges of its repository, as the forge says ancestry (issue 1946)	2026-10-24 17:03:20 +02:00
jschoubben	2139e83a8a	Remove a binary built by mistake	2026-10-24 16:58:33 +02:00
jschoubben	e7ca8f7af1	The backup module says on the bus when a backup asked for now has ended, so no one polls backed-up (issue 1944, ADR 0539 §16)	2026-10-24 16:58:19 +02:00
jschoubben	eb79996336	The tracker derives a fix's delivered from the delivery view's event, not the gate's gone states (issue 1946)	2026-10-24 16:50:50 +02:00
jschoubben	1a271a1fb1	The group's integration test hears the forge's merges once both members are handed (issue 1946, R6-C3)	2026-10-24 16:43:48 +02:00
jschoubben	30d04f6bef	Pin the gate to mesh-sdk's release 6 verb tables and prove it holds the seat as they have it (issue 1946, R6-C3) ... The integration tests hear the forge's own word that a pull request merged, as the real flow does, and fail on any call of the controller.	2026-10-24 16:35:15 +02:00
jschoubben	5ff337e0dc	Gate keeps the merge's six states and asks the controller nothing (issue 1946, R6-C1, C2, C4) ... Release 6 deletes the plans: the walk half of the holder, the controller port, the carry-over of the former module and the verbs times, what-if, release, stop and retire-history go; the table holds proposed, ready, rejected, merged, held and closed; the delivery's status and view name the source revision the merge moved.	2026-10-24 16:26:36 +02:00
jschoubben	2fabbe556e	Pin to the group's new mesh-sdk head bfc3883a, whose composer reads a fallback to a predefined key as the indexer does (ADR 0348 §7)	2026-10-24 14:57:35 +02:00
jschoubben	89b9212c4d	Pin to the group's new mesh-sdk head 19c1d359, whose composer names the reader's pinned SDK instead of a bare (devel) (ADR 0482 clause 5)	2026-10-24 14:12:09 +02:00
jschoubben	40da368ee3	Date an adopted merge once, by the walk it was adopted from, so a later walk it follows never makes it look newer than a forge merge heard after it (issue 1726, review)	2026-10-24 13:55:10 +02:00
jschoubben	865f3b6455	Say what pacman-tools reads outside: the root predefined.json (issue 1935)	2026-10-24 13:48:18 +02:00
jschoubben	03524ecd13	Mark pacman-tools as reading outside its directory: its upgrade-order test reads the root predefined.json, which its digest does not cover (issue 1935)	2026-10-24 13:48:09 +02:00
jschoubben	15101c9ce6	Move source.main for a merge the gate caught up after a gap, so the checker re-checks open heads on the trunk that is (issue 1726) ... The checker takes a repository's trunk head only from the gate's source.main. On 2026-10-24 gitea's restarted poll announced mesh-catalog #471's merge while the gate was starting and could not yet tell whether it held the seat; the gate acknowledged the event unread. It then adopted the controller's walk of the merge commit, which carries no merge time, so every older merge of the repository looked newer and source.main was never moved: #472 was checked on the trunk before #471 and its merge refused. - An event heard before the gate can tell whether it holds the seat is offered again, not taken. - An adopted merge is dated by its walk's creation, so it settles into source.main as a forge merge does. - Each time the gate comes to hold the seat it weighs the newest merge of each repository against source.main once more, so a merge marked there and never written (as #471) is written; never backwards.	2026-10-24 13:41:56 +02:00
jschoubben	f910b0ceb8	Pin mesh-build-go to the group's mesh-sdk head after main's merge, so it builds on the SDK the group delivers	2026-10-24 13:28:16 +02:00
jschoubben	91c3e954ae	Merge main into feat/r4g-finish (#471)	2026-10-24 13:26:24 +02:00
jschoubben	7afcd0282d	Set up the forge's webhook without holding the bundle's import, so a slow forge never costs gitea its handshake and its tools (issue 1726) ... At 12:37 on 2026-10-24 node-tools on novox was replaced; gitea's watcher bundle awaited the webhook's set-up on the forge's admin API at the top of its import, outlasted the 10 s handshake and was killed, never to start again. gitea_commit_status, gitea_merge_pull_request and gitea_events were then served nowhere: the forge bridge's calls found no responders and no new pull request was announced.	2026-10-24 13:00:57 +02:00
jschoubben	75156fce00	gitea: forge-account reads the forge's own host key file before scanning its sshd (issue 1939)	2026-10-24 12:50:20 +02:00
jschoubben	16d7b1898d	Mark the packages whose tests read files outside their directory, found by the review (issue 1935)	2026-10-24 04:38:49 +02:00
jschoubben	e870a7f65f	Pin to the finish group's mesh-sdk head dd0d156b, so every member names one SDK (issue 1622)	2026-10-24 04:28:14 +02:00
jschoubben	e8a59171c7	Merge remote-tracking branch 'origin/feat/r4g-finish-composer' into HEAD	2026-10-24 04:26:03 +02:00
jschoubben	6a70735489	Run a compose ask on the Go build seat: build mesh-sdk's composer at the asked commit once, fill its manifests from the indexer and run it shut off (issue 1622)	2026-10-24 04:14:21 +02:00
jschoubben	a715c8821f	mesh-build-go: a catalogue module's non-Go files enter its packages' digests; markers where tests read other modules (issue 1935)	2026-10-24 03:59:08 +02:00
jschoubben	b6ed8599c8	mesh-build-go: a package marked reads-outside is never kept, so tests that read files outside their directory run on every check (issue 1935)	2026-10-24 03:46:45 +02:00
jschoubben	7e1f3de77a	mesh-build-go: lint directories side by side like the tests, so a large repository's check stays inside its bound (issue 1930)	2026-10-24 02:01:36 +02:00
jschoubben	4b1bed4b9d	Merge pull request 'mesh-mail-reader: read messenger's sent_on as a list, so an unchanged set of mails is signalled once, not every 160 s (issue 1926)' (#469) from fix/1926-mail-signal-once into main ... Reviewed-on: #469	2026-10-23 22:36:10 +00:00
jschoubben	25d69406b7	Merge pull request 'mesh-build-go: a failed test keeps its last lines and its cause, not its first fifteen (issue 1901, with mesh-delivery)' (#466) from fix/1901-rebased into main ... Reviewed-on: #466	2026-10-23 22:35:57 +00:00
jschoubben	f836c021e1	Merge pull request 'gitea: the checker's owed results are taken at once and written in the background, so the runner keeps the watch and every mesh/check reaches the forge (issue 1726)' (#468) from fix/1726-owed-watch-not-blocked into main ... Reviewed-on: #468	2026-10-23 22:35:33 +00:00
jschoubben	5a7076a6a2	Take the checker's owed without waiting on the forge, so a large owed never times its watch out (issue 1726) ... The runtime gives a watch's current values 10 s and waits for each to be taken; a forge write per key made ~200 keys outlast it at every attempt, so after node-tools restarted on novox at 23:25:58 the watch never held and no verdict reached mesh/check. Writes now run in the background, a few at a time, each key's in revision order.	2026-10-23 23:52:52 +02:00