Say loudly what cannot be judged, read only a merge's changed directories, and move the taken key only by an applied merge (issues 1422, 1126; group fix/1422-trunk-unknown) #94

Merged

mesh-tools merged 7 commits from fix/1422-trunk-unknown into main 2026-10-28 10:34:51 +00:00

Conversation 1 Commits 7 Files Changed 21

+679 -90

7 Commits

Author	SHA1	Message	Date
jschoubben	2b801f5bd4	indexer_take_in reads a held module again only when its record is behind the source's head, and the two new tests are rows (issue 1126, review) ... A head older than the record, or one whose order the forge cannot say, would have written an older manifest back. The new tests become rows of existing ones: the repository is over its 500 unit tests.	2026-10-28 11:18:01 +01:00
jschoubben	790653dfde	indexer_take_in reads a held module again at the source's head when its record stands behind it (issue 1126) ... A merge whose merged message never reached the indexer had no recovery: take-in answered held for mesh-vault, whose record stayed at 78d7ef7 after mesh-catalog#535.	2026-10-28 11:10:09 +01:00
jschoubben	89be76bb6a	The forge bridge keeps the directories a failed try read whole, so a large merge converges over its tries (issue 1126) ... Without it the first merge after the bridge starts, with nothing kept, still reads all 140 catalogue directories in one 30 s try and times out as before.	2026-10-28 11:10:09 +01:00
jschoubben	704fc8d467	The forge bridge reads a merge's module directories only where their tree changed (issue 1126) ... mesh-catalog's 140 module directories are 420 forge reads per merge, past the 30 s bound of a handled event while the forge is busy: the merged message of #535 timed out on every try, and #3fb7951 needed seven (issue 1458 met the same kind at 131). A tree hash names its bytes, so what was read at a tree is kept in the new state inputs and in memory, and a merge reads only the directories it changed.	2026-10-28 11:10:09 +01:00
jschoubben	458e403a04	The indexer's taken key moves only by a merge it applied, never by the gate's source head (issue 1126) ... A drained forge stream does not say a merge was applied: the forge bridge was still retrying mesh-catalog#535's merged message when the indexer started, and the source's head moved taken.mesh-catalog to 9fd9569, so the view and show said the merge was on the machines while mesh-vault's record stood at 78d7ef7 (ADR 0556 clause 1).	2026-10-28 11:10:09 +01:00
jschoubben	93c0ae19dd	Forge bridge: write a head pushed to a pull request into another base as closed, and say so (issue 1422) ... The checker judges pull requests into main only and source.main names main's head only (ADR 0484 §11), but a live update into another base (de-spiegel#6 into nox-mesh) became a candidate, unlike at the start (OpenPulls) and at its merge. Once the gate seeds a repository's trunk head, such a candidate would be judged against main's head: a verdict that lies.	2026-10-28 11:03:39 +01:00
jschoubben	4e9b076408	Checker: say loudly that a pull request cannot be judged when its repository has no trunk head (issue 1422) ... A repository never merged through the gate has no entry in source.main, so its pull requests were dropped without a log line, a verdict or a status, and checker_status counted them as new. Now the verdict says it cannot be judged and why, the forge status is error with those words, checker_status names it under cannot_be_judged, the log says it once per head, and the heads are judged whole once the trunk head is known. Quick fix: this. Thorough fix (the gate seeding source.main from the pull message's base head) is still to do: it needs mesh-sdk, the forge bridge and the gate.	2026-10-28 11:03:39 +01:00