mesh-build-go: a merge preview names a path and a path inside it (mesh-contracts' go), and a step's cause keeps the module Go could not find (issue 1966)
#613
Merged
mesh-toolsmerged 2 commits from fix/buildstep-preview into main2026-11-04 19:44:21 +00:00
A fix of the checking tool, delivered before the registry milestone's group (issue 1966): its group check failed because buildstep's narrow ran one git ls-tree over "go" and "go/seats/x", so git listed go's children and "go" got no object ("the module . names the path go, which is not in "), and the step's cause cut Go's error at "requires". The group check runs the build module the mesh runs, so this goes first.
narrow asks git once per round of paths none of which lies inside another (one round in the common case); the cause keeps Go's indented continuation lines. Rows of existing tests only; mesh-build-go 253 unit, 26 integration.
Quick or thorough: thorough here is the same change (the one reader of manifest paths), held by its real-git row.
A fix of the checking tool, delivered before the registry milestone's group (issue 1966): its group check failed because buildstep's narrow ran one git ls-tree over "go" and "go/seats/x", so git listed go's children and "go" got no object ("the module . names the path go, which is not in <merge>"), and the step's cause cut Go's error at "requires". The group check runs the build module the mesh runs, so this goes first.
narrow asks git once per round of paths none of which lies inside another (one round in the common case); the cause keeps Go's indented continuation lines. Rows of existing tests only; mesh-build-go 253 unit, 26 integration.
Quick or thorough: thorough here is the same change (the one reader of manifest paths), held by its real-git row.
Reviewed-by: review-catalog@shanks at da2aa918322145198eb6def10ae36133adae7f71
https://claude.ai/code/session_01JG73KJNrH5EgFXMKKYSrig
Deliverynovox/mesh-catalog@da2aa9183221 — merged since 2026-11-04T19:44:23Z
Source — source.main moved to novox/mesh-catalog@fd4931a752. Whether it reached the machines is mesh-delivery-view's, derived from source.main, the wants and the haves.
Transitions
2026-11-04 19:23 (new) → proposed (announced): novox/mesh-catalog#613's head announced
2026-11-04 19:23 proposed → ready (accepted): a verdict names this commit and the trunk's head as its trunk commit, the gate passed or warned, and the repository's own check did not fail; or the check gates no merge (check-gates-merge false)
2026-11-04 19:44 ready → merged (merged): on the trunk its modules follow: merged there
The commit's note under refs/notes/mesh-plan keeps every transition of this change up to its merge: git log --notes=mesh-plan.
<!-- mesh-delivery:view -->
**Delivery** `novox/mesh-catalog@da2aa9183221` — **merged** since 2026-11-04T19:44:23Z
**Source** — source.main moved to novox/mesh-catalog@fd4931a75261. Whether it reached the machines is `mesh-delivery-view`'s, derived from `source.main`, the wants and the haves.
**Transitions**
- 2026-11-04 19:23 (new) → proposed (announced): novox/mesh-catalog#613's head announced
- 2026-11-04 19:23 proposed → ready (accepted): a verdict names this commit and the trunk's head as its trunk commit, the gate passed or warned, and the repository's own check did not fail; or the check gates no merge (check-gates-merge false)
- 2026-11-04 19:44 ready → merged (merged): on the trunk its modules follow: merged there
The commit's note under `refs/notes/mesh-plan` keeps every transition of this change up to its merge: `git log --notes=mesh-plan`.
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
A fix of the checking tool, delivered before the registry milestone's group (issue 1966): its group check failed because buildstep's narrow ran one git ls-tree over "go" and "go/seats/x", so git listed go's children and "go" got no object ("the module . names the path go, which is not in "), and the step's cause cut Go's error at "requires". The group check runs the build module the mesh runs, so this goes first.
narrow asks git once per round of paths none of which lies inside another (one round in the common case); the cause keeps Go's indented continuation lines. Rows of existing tests only; mesh-build-go 253 unit, 26 integration.
Quick or thorough: thorough here is the same change (the one reader of manifest paths), held by its real-git row.
Reviewed-by: review-catalog@shanks at
da2aa91832https://claude.ai/code/session_01JG73KJNrH5EgFXMKKYSrig
Delivery
novox/mesh-catalog@da2aa9183221— merged since 2026-11-04T19:44:23ZSource — source.main moved to novox/mesh-catalog@fd4931a752. Whether it reached the machines is
mesh-delivery-view's, derived fromsource.main, the wants and the haves.Transitions
The commit's note under
refs/notes/mesh-plankeeps every transition of this change up to its merge:git log --notes=mesh-plan.