The provisioner reads a provider's outcome per offer and reads route-proxy and node-tools, so gitea's credentials, routes and mcp endpoints are provided (issue 774) #568

2026-10-30T20:31:04Z

mesh-tools commented

2026-10-30 20:31:04 +00:00

8 provisions failed ("gitea does not serve" for gitea-read and npm-package-registry) and 6 stood asked (route, mcp-endpoint). keepsEntriesFor judges an offer answered-by helper by the helper's entries and any other by the module's have; gitea's forge-account offer says answered-by helper; BoundReads and the manifest read route-proxy.bound and node-tools.bound. TestAProvidersOutcomeIsReadPerOffer replays the live keys.

Group fix/held-module-and-assigner-contract (mesh-sdk, mesh-host, mesh-delivery, mesh-catalog), issue 774. The lead merges once mesh/check and mesh/delivery-group are green (operator, 2026-10-30 20:41); mesh-sdk first.
Reviewed-by: rev-sweep@shanks at b8ce4f0c0a

8 provisions failed ("gitea does not serve" for gitea-read and npm-package-registry) and 6 stood asked (route, mcp-endpoint). keepsEntriesFor judges an offer answered-by helper by the helper's entries and any other by the module's have; gitea's forge-account offer says answered-by helper; BoundReads and the manifest read route-proxy.bound and node-tools.bound. TestAProvidersOutcomeIsReadPerOffer replays the live keys. Group fix/held-module-and-assigner-contract (mesh-sdk, mesh-host, mesh-delivery, mesh-catalog), issue 774. The lead merges once mesh/check and mesh/delivery-group are green (operator, 2026-10-30 20:41); mesh-sdk first. Reviewed-by: rev-sweep@shanks at b8ce4f0c0ac587d270de04cf4a18def22e5f96f0

mesh-tools added 1 commit 2026-10-30 20:31:04 +00:00

Read a provider's outcome per offer, and read route-proxy's and node-tools' entries, so provisions a helper does not answer stop failing and routed keys stop standing asked (issue 774)

mesh/delivery-group group fix/held-module-and-assigner-contract rejected: composed together: the checker's verdict at the members' heads (c82f18b5e6bb): integr…

Details

mesh/delivery closed: the pull request closed unmerged

Details

mesh/check failed: integration: mesh-healers/cmd/mesh-healers.TestTheHealersWholeActOnTheBusAndBrake: never: the would-act written | b8ce4f0c0ac5 on 3…

b8ce4f0c0a

The sweep of 2026-10-30 20:10: <node>.claude-code.gitea-read and <node>.mesh-build-node.npm-package-registry failed on
all four nodes with "gitea does not serve": gitea's provider helper answers only forge-account and refuses every other
bind into gitea.bound, and the provisioner took any entry of a module declaring `bound` as the outcome. And
novox.gitea.route, novox.keycloak.route and <node>.claude-code.mcp-endpoint stood asked: route-proxy and node-tools keep
entries the manifest did not read.

Quick fix: add route-proxy.bound and node-tools.bound to the reads. Thorough fix: judge each offer by who answers it
(answered-by: helper reads the entries, any other offer of a module that names a helper is judged by its have), and say
on gitea's forge-account that the helper answers it. Chose both: the reads alone leave gitea's two provisions failed.

mesh-tools commented

2026-10-30 20:31:09 +00:00

Delivery novox/mesh-catalog@b8ce4f0c0ac5 — closed since 2026-10-30T20:59:43Z

Group fix/held-module-and-assigner-contract: novox/mesh-delivery@8fe6442c47, novox/mesh-host@62cfb45789, novox/mesh-sdk@eff81f1220

Transitions

2026-10-30 20:31 (new) → proposed (announced): novox/mesh-catalog#568's head announced
2026-10-30 20:31 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 20:59 ready → closed (closed): the pull request closed unmerged

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@b8ce4f0c0ac5` — **closed** since 2026-10-30T20:59:43Z **Group** `fix/held-module-and-assigner-contract`: novox/mesh-delivery@8fe6442c4754, novox/mesh-host@62cfb45789c1, novox/mesh-sdk@eff81f1220e2 **Transitions** - 2026-10-30 20:31 (new) → proposed (announced): novox/mesh-catalog#568's head announced - 2026-10-30 20:31 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 20:59 ready → closed (closed): the pull request closed unmerged 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 closed this pull request

2026-10-30 20:59:41 +00:00

mesh-tools referenced this pull request

2026-10-30 20:59:43 +00:00

The provisioner reads a provider's outcome per offer, and modules subscribe before they wait, so gitea's credentials, routes and early events are not lost (issue 774) #571

mesh-tools commented

2026-10-30 20:59:46 +00:00

mesh-delivery: the operator's Approve of this pull request's merge into main is ended: a head it covers moved on: the heads it covers are no longer the group's heads. Nothing is merged on it. The operator is asked again once the checks pass at the new head.

Pull request closed

This pull request cannot be reopened because the branch was deleted.

Sign in to join this conversation.

1 Participants

Notifications

Due Date

No due date set.

Dependencies

No dependencies set.

Reference: novox/mesh-catalog#568