Issue 1890. Delivery group fix/1890-left-running-steps with mesh-sdk (this head pins its head, v0.1.14-0.20261026125154-6b8497314297).
mesh-build-go, mesh-build-node and mesh-build-image call the sdk's EndStaleAtStart from main.go and EndStaleRound in their existing Start loop beside CleanWorkspaces, and serve build_go_step_end, build_node_step_end, build_image_step_end {id, why} (named in each module.json). Step lists show what.
After delivery: the 17 steps mesh-delivery-checker.checker_status lists under left_running (all asks started before 12:02 UTC) are ended by each module's start or its next round (within 10 minutes), reason "past the step bound".
Tests: what assertions in the step-list tests; the new tool in the manifest skip lists. Unit suites and go vet -tags integration ./... clean.
Rule bent (rules-are-weighed): no try at this head; a catalogue head pinning an unmerged sdk head can only be judged with its sdk pull request in the group, and the try places were full. The group's merge check is the gate.
Issue 1890. Delivery group fix/1890-left-running-steps with mesh-sdk (this head pins its head, v0.1.14-0.20261026125154-6b8497314297).
mesh-build-go, mesh-build-node and mesh-build-image call the sdk's `EndStaleAtStart` from main.go and `EndStaleRound` in their existing Start loop beside CleanWorkspaces, and serve `build_go_step_end`, `build_node_step_end`, `build_image_step_end` {id, why} (named in each module.json). Step lists show `what`.
After delivery: the 17 steps `mesh-delivery-checker.checker_status` lists under left_running (all asks started before 12:02 UTC) are ended by each module's start or its next round (within 10 minutes), reason "past the step bound".
Tests: `what` assertions in the step-list tests; the new tool in the manifest skip lists. Unit suites and `go vet -tags integration ./...` clean.
Rule bent (rules-are-weighed): no try at this head; a catalogue head pinning an unmerged sdk head can only be judged with its sdk pull request in the group, and the try places were full. The group's merge check is the gate.
Reviewed-by: review-1890@shanks at 0134697f9739f652e9b2a80a14480bb476f2454d
Deliverynovox/mesh-catalog@0134697f9739 — merged since 2026-10-26T12:57:38Z
Source — source.main moved to novox/mesh-catalog@b1e610b213. Whether it reached the machines is mesh-delivery-view's, derived from source.main, the wants and the haves.
2026-10-26 12:54 (new) → proposed (announced): novox/mesh-catalog#496's head announced
2026-10-26 12:54 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-10-26 12:57 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@0134697f9739` — **merged** since 2026-10-26T12:57:38Z
**Source** — source.main moved to novox/mesh-catalog@b1e610b2135a. Whether it reached the machines is `mesh-delivery-view`'s, derived from `source.main`, the wants and the haves.
**Group** `fix/1890-left-running-steps`: novox/mesh-catalog@0134697f9739, novox/mesh-sdk@6b8497314297
**Transitions**
- 2026-10-26 12:54 (new) → proposed (announced): novox/mesh-catalog#496's head announced
- 2026-10-26 12:54 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-10-26 12:57 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.
Issue 1890. Delivery group fix/1890-left-running-steps with mesh-sdk (this head pins its head, v0.1.14-0.20261026125154-6b8497314297).
mesh-build-go, mesh-build-node and mesh-build-image call the sdk's
EndStaleAtStartfrom main.go andEndStaleRoundin their existing Start loop beside CleanWorkspaces, and servebuild_go_step_end,build_node_step_end,build_image_step_end{id, why} (named in each module.json). Step lists showwhat.After delivery: the 17 steps
mesh-delivery-checker.checker_statuslists under left_running (all asks started before 12:02 UTC) are ended by each module's start or its next round (within 10 minutes), reason "past the step bound".Tests:
whatassertions in the step-list tests; the new tool in the manifest skip lists. Unit suites andgo vet -tags integration ./...clean.Rule bent (rules-are-weighed): no try at this head; a catalogue head pinning an unmerged sdk head can only be judged with its sdk pull request in the group, and the try places were full. The group's merge check is the gate.
Reviewed-by: review-1890@shanks at
0134697f97Delivery
novox/mesh-catalog@0134697f9739— merged since 2026-10-26T12:57:38ZSource — source.main moved to novox/mesh-catalog@b1e610b213. Whether it reached the machines is
mesh-delivery-view's, derived fromsource.main, the wants and the haves.Group
fix/1890-left-running-steps: novox/mesh-catalog@0134697f97, novox/mesh-sdk@6b84973142Transitions
The commit's note under
refs/notes/mesh-plankeeps every transition of this change up to its merge:git log --notes=mesh-plan.