The assigner says when it holds the bus back instead of skipping it silently (issue 1945) #70

2026-10-26T13:12:07Z

mesh-tools commented

2026-10-26 13:12:07 +00:00

Issue 1945 (notes 91). Since the switch to wants the bus module nats has had no want on novox and nothing said so: the assigner's bus bar (ADR 0539 §15, ADR 0546 §8: only the operator's put moves the bus) skipped the node with continue, so it was on no list, and pass.go cleared the neither-list condition after every start logging "nats on novox has a want again" although it has none.

The bar is unchanged (busBar, same expression; still no want that moves the bus). When it stops a move, the pass records a holding with plain words ("only your put moves the bus: runs , the trunk builds ; put it with assigner_put") and puts the node on neither list when it has no live want.
The bus's neither condition says "Needs you: put nats on novox with assigner_put" and stays raised. A clear says "has a want again" only with a live want; otherwise why there is none (held, a put that still owns the want, no trunk build, the rule's words, or the node does not run it).

What the operator will see after delivery: one urgent message "nats on novox is on no list" (Needs you: put nats on novox), once, with one reminder an hour later, until the bus is put. The bus upgrade it asks for (7842001c -> 9d9dfda1, a bus restart) is asked separately.

Tests: rows in the existing bus test (wants_test.go), the neither test (pass_test.go, incl. a put in progress and an ended put) and the sayNoWant table; they fail on main. Unit suite and go vet -tags integration ./... clean. Tries passed at each head, last try-1793019963189959313.

Reviewed-by: review-busbar@shanks at 2d841870a8

Issue 1945 (notes 91). Since the switch to wants the bus module nats has had no want on novox and nothing said so: the assigner's bus bar (ADR 0539 §15, ADR 0546 §8: only the operator's put moves the bus) skipped the node with `continue`, so it was on no list, and pass.go cleared the neither-list condition after every start logging "nats on novox has a want again" although it has none. - The bar is unchanged (`busBar`, same expression; still no want that moves the bus). When it stops a move, the pass records a holding with plain words ("only your put moves the bus: <node> runs <prev>, the trunk builds <fp>; put it with assigner_put") and puts the node on neither list when it has no live want. - The bus's neither condition says "Needs you: put nats on novox with assigner_put" and stays raised. A clear says "has a want again" only with a live want; otherwise why there is none (held, a put that still owns the want, no trunk build, the rule's words, or the node does not run it). What the operator will see after delivery: one urgent message "nats on novox is on no list" (Needs you: put nats on novox), once, with one reminder an hour later, until the bus is put. The bus upgrade it asks for (7842001c -> 9d9dfda1, a bus restart) is asked separately. Tests: rows in the existing bus test (wants_test.go), the neither test (pass_test.go, incl. a put in progress and an ended put) and the sayNoWant table; they fail on main. Unit suite and `go vet -tags integration ./...` clean. Tries passed at each head, last try-1793019963189959313. Reviewed-by: review-busbar@shanks at 2d841870a873d877b068559297187d75417f3db9

mesh-tools added 3 commits 2026-10-26 13:12:07 +00:00

Assigner: say the bus bar instead of skipping it silently, and clear a neither condition only in true words (issue 1945) 2d63f0ba62

A bus whose move only the operator's put may make (ADR 0546 §8) got no want and nothing in the outcome:
nats on novox, running an old-form build, was on no list while the pass cleared its condition and logged
that it had a want again. The bar now names its holding, puts a node without a live want on neither list
(its condition needs the operator: assigner_put), and a neither condition is cleared as 'has a want again'
only when a live want exists.

Assigner: name a running put when a node leaves neither list, and say the bus bar in plain words (issue 1945) f4aac599ca

Review round 1: while an operator's put runs through its steps it owns the want, so the clear said
'the node does not run it' of a node that runs the bus.

Assigner: only a put still on its steps is named when a node leaves neither list (issue 1945)

mesh/delivery merged: source.main moved to novox/mesh-delivery@c8b26735c8cf

Details

mesh/check pass 2d841870a873 on c8b26735c8cf | carried from 1d416827157d | unit 185 run, 518 kept | integration 195 run, 584 kept | composition passed…

2d841870a8

Review round 2: an ended put stays in the bucket and owns no want.

mesh-tools commented

2026-10-26 13:12:11 +00:00

Delivery novox/mesh-delivery@2d841870a873 — merged since 2026-10-26T13:13:24Z

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

Transitions

2026-10-26 13:12 (new) → proposed (announced): novox/mesh-delivery#70's head announced
2026-10-26 13:12 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 13:13 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-delivery@2d841870a873` — **merged** since 2026-10-26T13:13:24Z **Source** — source.main moved to novox/mesh-delivery@c8b26735c8cf. Whether it reached the machines is `mesh-delivery-view`'s, derived from `source.main`, the wants and the haves. **Transitions** - 2026-10-26 13:12 (new) → proposed (announced): novox/mesh-delivery#70's head announced - 2026-10-26 13:12 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 13:13 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 c8b26735c8 into main

2026-10-26 13:13:22 +00:00

mesh-tools deleted branch fix/bus-bar-loud

2026-10-26 13:13:23 +00:00

Sign in to join this conversation.

1 Participants

Notifications

Due Date

No due date set.

Dependencies

No dependencies set.

Reference: novox/mesh-delivery#70