Let the build modules follow their capacity on the bus, so a node raised from capacity 0 starts pulling (issue 1887) #479

2026-10-25T16:46:59Z

mesh-tools commented

2026-10-25 16:46:59 +00:00

mesh-build-go, mesh-build-node and mesh-build-image take the mesh-sdk puller that wakes on its capacity's change (mesh-sdk fix/puller-wakes-on-capacity, a8fbabbf), so raising a node's capacity from 0 starts its builds without a hand resume.

Issue: https://git.novox.be/novox/hq (issue 1887, note 15).

Merge AFTER the mesh-sdk pull request of the same branch (this pins its head v0.1.14-0.20261025164403-a8fbabbfc373). mesh-build-node and mesh-build-image also move from SDK 403a5d72 to that head, taking in mesh-sdk #77-#79; their builds and unit tests pass.

Tests: build, vet (with and without -tags integration) and unit tests pass in all three modules (164, 89, 52). No tests added. Recovery mode: no try; the operator merges by hand.

Live proof after delivery: raising g14's mesh-build-go capacity from 0 logs 'build capacity of g14 is N' and 'wakes' and takes a waiting ask.

Reviewed-by: reviewer-puller@shanks at 23c827e791

mesh-build-go, mesh-build-node and mesh-build-image take the mesh-sdk puller that wakes on its capacity's change (mesh-sdk fix/puller-wakes-on-capacity, a8fbabbf), so raising a node's capacity from 0 starts its builds without a hand resume. Issue: https://git.novox.be/novox/hq (issue 1887, note 15). Merge AFTER the mesh-sdk pull request of the same branch (this pins its head v0.1.14-0.20261025164403-a8fbabbfc373). mesh-build-node and mesh-build-image also move from SDK 403a5d72 to that head, taking in mesh-sdk #77-#79; their builds and unit tests pass. Tests: build, vet (with and without -tags integration) and unit tests pass in all three modules (164, 89, 52). No tests added. Recovery mode: no try; the operator merges by hand. Live proof after delivery: raising g14's mesh-build-go capacity from 0 logs 'build capacity of g14 is N' and 'wakes' and takes a waiting ask. Reviewed-by: reviewer-puller@shanks at 23c827e7910c233608af4e4a8056cbc362dcb755

mesh-tools added 2 commits 2026-10-25 16:46:59 +00:00

Let the build modules follow their capacity on the bus, so a node raised from capacity 0 starts pulling (issue 1887) 3138570c6b

g14's Go builder sat idle at capacity 2 because nothing woke its parked
puller. mesh-build-go, mesh-build-node and mesh-build-image now pin mesh-sdk
b9911dc1, whose puller watches the config value capacity as mesh-config
resolved it and wakes on each change, and hand it that watch.

Take the mesh-sdk head that wakes a puller on its capacity, within the test budget, in the three build modules (issue 1887)

mesh/delivery merged: source.main moved to novox/mesh-catalog@2df0503034dc

Details

mesh/check pass 23c827e7910c on a85d90374195 | judged by the candidate's mesh-build-go at eab02c80fe86

mesh/delivery-group group fix/puller-wakes-on-capacity merged: every member is merged

Details

23c827e791

mesh-tools commented

2026-10-25 16:47:04 +00:00

Delivery novox/mesh-catalog@23c827e7910c — merged since 2026-10-25T17:02:43Z

Source — source.main moved to novox/mesh-catalog@2df0503034. Whether it reached the machines is mesh-delivery-view's, derived from source.main, the wants and the haves.

Group fix/puller-wakes-on-capacity: novox/mesh-catalog@23c827e791, novox/mesh-sdk@a8fbabbfc3

composed together: pass — the checker's verdict at the members' heads (71a936cf38ad)

Transitions

2026-10-25 16:47 (new) → proposed (announced): novox/mesh-catalog#479's head announced
2026-10-25 16:56 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
2026-10-25 17:02 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.

**Delivery** `novox/mesh-catalog@23c827e7910c` — **merged** since 2026-10-25T17:02:43Z **Source** — source.main moved to novox/mesh-catalog@2df0503034dc. Whether it reached the machines is `mesh-delivery-view`'s, derived from `source.main`, the wants and the haves. **Group** `fix/puller-wakes-on-capacity`: novox/mesh-catalog@23c827e7910c, novox/mesh-sdk@a8fbabbfc373 - composed together: pass — the checker's verdict at the members' heads (71a936cf38ad) **Transitions** - 2026-10-25 16:47 (new) → proposed (announced): novox/mesh-catalog#479's head announced - 2026-10-25 16:56 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 - 2026-10-25 17:02 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-tools merged commit 2df0503034 into main

2026-10-25 17:02:41 +00:00

mesh-tools deleted branch fix/puller-wakes-on-capacity

2026-10-25 17:02:41 +00:00

mesh-tools referenced this pull request

2026-10-25 17:40:12 +00:00

Gate: hand every member of an approved group in pin order, settle pull requests closed on the forge, and say a stopped pass as a condition (issue 1275) #480

Sign in to join this conversation.

1 Participants

Notifications

Due Date

No due date set.

Dependencies

No dependencies set.

Reference: novox/mesh-catalog#479