The provisioner says why a key stays asked when its provider reads no plans of the seat (issue 774) #575

2026-10-30T23:32:17Z

mesh-tools commented

2026-10-30 23:32:17 +00:00

Issue 774 (L3). 38 route provisions stayed "asked" with an empty reason tonight, because route-proxy's helper still read the controller's assignments and never the seat's plans (fixed separately in mesh-control fix/route-proxy-reads-plans). The provisioner now names that case: an asked key with no entry from a helper-answered provider whose manifest reads no mesh-provisioner.plans gets the reason " reads no plans of the seat ... so its helper never answers this key", instead of staying asked in silence.

Quick vs thorough: this is part of the thorough fix (say the silent case); the catalogue check that refuses a helper-answered provider without the seat's reads is the next part. New row in TestAProvidersOutcomeIsReadPerOffer, fails on main. gofmt, vet (both tags), go test pass in modules/mesh-provisioner.

Reviewer notes (not findings): unread checks PlansRead only, not provisions; two extra KV reads per unanswered key.

Reviewed-by: rev-routes@shanks at bb18c4d14f

Issue 774 (L3). 38 route provisions stayed "asked" with an empty reason tonight, because route-proxy's helper still read the controller's assignments and never the seat's plans (fixed separately in mesh-control fix/route-proxy-reads-plans). The provisioner now names that case: an asked key with no entry from a helper-answered provider whose manifest reads no mesh-provisioner.plans gets the reason "<provider> reads no plans of the seat ... so its helper never answers this key", instead of staying asked in silence. Quick vs thorough: this is part of the thorough fix (say the silent case); the catalogue check that refuses a helper-answered provider without the seat's reads is the next part. New row in TestAProvidersOutcomeIsReadPerOffer, fails on main. gofmt, vet (both tags), go test pass in modules/mesh-provisioner. Reviewer notes (not findings): unread checks PlansRead only, not provisions; two extra KV reads per unanswered key. Reviewed-by: rev-routes@shanks at bb18c4d14fc33fa8ecd866b077cfe0d732b3c9b9

mesh-tools added 1 commit 2026-10-30 23:32:17 +00:00

Say why a key stays asked when its provider's helper reads no plans of the seat, so a provider left on the controller's assignments is named instead of waited on in silence (issue 774)

mesh/delivery merged: source.main moved to novox/mesh-catalog@0e78909a75b9

Details

mesh/check being carried to bb18c4d14fc3 on 0e78909a75b9 | from d412991c6992

bb18c4d14f

mesh-tools commented

2026-10-30 23:32:19 +00:00

Delivery novox/mesh-catalog@bb18c4d14fc3 — merged since 2026-10-30T23:43:15Z

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

Transitions

2026-10-30 23:32 (new) → proposed (announced): novox/mesh-catalog#575's head announced
2026-10-30 23:32 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-30 23:43 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@bb18c4d14fc3` — **merged** since 2026-10-30T23:43:15Z **Source** — source.main moved to novox/mesh-catalog@0e78909a75b9. Whether it reached the machines is `mesh-delivery-view`'s, derived from `source.main`, the wants and the haves. **Transitions** - 2026-10-30 23:32 (new) → proposed (announced): novox/mesh-catalog#575's head announced - 2026-10-30 23:32 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-30 23:43 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 0e78909a75 into main

2026-10-30 23:43:14 +00:00

mesh-tools deleted branch fix/holder-says-unread-plans

2026-10-30 23:43:14 +00:00

Sign in to join this conversation.

1 Participants

Notifications

Due Date

No due date set.

Dependencies

No dependencies set.

Reference: novox/mesh-catalog#575