6 Commits

Include renames

Author	SHA1	Message	Date
jschoubben	907e092abc	mesh-delivery-indexer reads unread registered modules again in one background run, so a forge timeout holds no merged message or source revision past its ack wait (issue 1945, review round 1) ... The take-in tool's bound now says the take-in is still running and where its answer will be.	2026-10-26 14:11:12 +01:00
jschoubben	07b5f13474	mesh-delivery-indexer reads a registered module again once its repository becomes readable, and takes one in on ask (issue 1945) ... A registered module whose repository the forge answered 404 (car-hunter, snake, before the forge's account could read them) was read again only when the indexer started again or the controller wrote a new build record of it, so the grants part's composed user list stayed short of their subjects and the take-over was refused. A failed read now keeps the module as unread, read again on the next source revision and the next merged message (no timer of its own), and the new tool indexer_take_in (the tools bundle mesh-delivery-indexer-tools, through the indexer's takeins state, as the builder's builder_ask_again) takes one in now and answers what it stored or why not.	2026-10-26 14:01:34 +01:00
jschoubben	eaf27f36af	Write a module's value only when the module changed, so a merge no longer rewrites every module of its repository ... The operator, 2026-10-25: only if a module has a new version in commit x is a new value written naming commit x. A merge wrote every module of the repository at the new commit, fingerprint unchanged (about 186 keys per mesh-catalog merge), and the controller's take-in took each in again: twice tonight it flooded. Now a merge that gives a module the value it holds but for the commit writes nothing, and the value keeps the commit its fingerprint first appeared at. The kind: a write that differs only in where it was computed. The other instance, a source revision re-stamping Src on every module at its repository's head after any merge anywhere, now stamps Src once. The trunk head stays the gate's source.main.	2026-10-25 21:13:59 +01:00
jschoubben	9f7e082688	List a repository's modules from the merged message's manifests and the indexer's own bucket, not the controller's build records, so a new module gets a value and a key with no build asked (issue 1851, I1 I2 I4, ADR 0501 §6, ADR 0453 §6) ... I1: a merge writes each module its manifests name, at its directory. I2: a pull request's changed directory, a preview's touched module and a source revision's modules come from the modules bucket (a module a pull request adds is found in the preview by its manifest). I4: the value of today's form (fp, none) is no longer written, since it was computed from the build records; mesh-sdk keeps it readable until R4g. One commit: the three share applyMerged and its tests. Pins mesh-sdk feat/r4e-sdk 9cb4d59.	2026-10-22 18:08:48 +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
mesh-tools	05c180cf87	Add the indexer's source revision logic and its tests that the last commit named (issue 1344)	2026-10-20 00:31:19 +00:00