Files
hq/04-ISSUES/252-a-merges-changed-modules-were-read-wrong/00-report.md
T
jschoubben ea0c62355c
mesh/delivery merged: source.main moved to novox/hq@c2f4bb2d485d
mesh/delivery-group group words/catalog merged: every member is merged
mesh/check pass ea0c62355c1c on eec73b8af0d7 | carried from 292232dad226 | unit 39 run, 0 kept, 1 skipped | integration 39 run, 0 kept, 1 skipped | co…
The glossary's word is catalog: replace the spelling catalogue in running prose
2026-10-28 11:27:34 +01:00

1.7 KiB

opened
opened
2026-10-05

252 — A merge's changed modules were read wrong, in both directions

What was observed

Each of three merges to the catalog within four minutes planned 99 to 100 modules, and rebuilt modules they did not touch. The outputs were identical, so nothing was redeployed. The rebuilds cost the build machine minutes for every merge.

Diagnosis

Too many. The controller treats a changed path outside every module directory it knows as shared code, and rebuilds every module built from the repository. A new module's directory, or one being removed, counts: the module is registered only after the merge is planned. Each of the three merges added or removed a module. The build agent, built from the same repository, then joins the set and becomes tier 0.

Too few. The forge's module asked for a hundred changed files and was given fifty, the forge's page size, and reported the list as whole. A merge of 59 files reached the controller with 50. Had the full rebuild not hidden it, a module whose own files changed would have stayed unbuilt.

Fix

  • The forge's module reads every page of a pull request's files.
  • The controller counts a changed path in a sibling of known module directories as that module's own, not shared, when that module's definition is among the changed paths. A sibling without a definition, such as a shared library, still means everything, which is the safe direction. Root files still mean everything.

Resolved — 2026-10-05

The forge's module reads every page of a pull request's files. The controller counts a new module's own directory as that module's when its definition is among the changed paths. Live: catalog merges planned one module each.