5 Commits

Include renames

Author	SHA1	Message	Date
jochen	f4fb0a7461	Name the package each controller-repository image compiles, and say a renamed file under both names (hq ADR 0267, issue 363) ... Every merge to the controller's repository rebuilt the route proxy and the build seat's holder, because their builds read that repository whole. Named, the build seat hands each only its program's build source and the planner moves each only when that changes. A rename was said under its new name alone, so a file moved out of a build source changed nothing the planner could see.	2026-10-10 02:58:31 +02:00
jochen	1178db279e	gitea: say which changed directories hold a module at the merge commit (hq issue 278) ... The controller read a changed file as shared code unless its directory was a module it holds or the merge also changed that directory's manifest. A merge touching modules/showcase/index.ts - the catalogue's reference module, held by no machine - therefore rebuilt all 103 modules built from this repository on 2026-10-06, 88 of them byte-identical, with the build agent first only because everything else is built by it. Whether a directory is a module is a fact of the repository at the commit, so the announcer now looks it up: every directory above a changed file (never the root) is asked for its module.json at the merge commit, and the ones that have one go out as module_dirs, with module_dirs_said. Not said when the file list is cut, past 300 directories, or when the forge cannot be asked; the controller then keeps its old rule, which rebuilds too much rather than too little. modules/showcase stays: TestTheShowcaseModuleIsAValidManifest in mesh-controller parses it and hq to-be 18 and 20 name it as the reference module.	2026-10-06 19:55:17 +02:00
jochen	1fd2914ae1	Say which modules wait for a person's push, and announce the files a merge deleted (hq ADR 0236) ... With a gate on the first machine and a rollback after it, a module's build rolls out by default. The ones kept back say why: the network path a rollback could not cross, the providers every consumer on a machine drops with, and the stores holding the photos. A merge's deleted files are announced, so a module whose manifest went is forgotten rather than asked to build (the public-acme plan failure).	2026-10-06 18:39:13 +02:00
jochen	52b81d524c	gitea: a merge poll looks only at repositories that moved, one pass at a time ... With the poll the only announcer of a merge, its cost showed: every 30 s it asked every repository for its pull requests, a pass outlasted the tick, and passes piled up beside each other — a merge was announced four and a half minutes late, and two passes at once could each announce it. A pass now asks only repositories updated since a minute before the last look, and the next pass starts when this one ends. hq issue 250.	2026-10-05 18:12:11 +02:00
jochen	45507c3d5c	gitea: test that a pull request's files are read past the forge's page cap	2026-10-05 17:47:36 +02:00