Take mesh-sdk 90b20f5, so node-files' contract names upload and download (issue 1718, design 60 F3 group) #424

Merged

mesh-tools merged 3 commits from feat/files-through-the-store into main 2026-10-21 16:31:28 +00:00

Conversation 2 Commits 3 Files Changed 6

+45 -5

mesh-tools commented 2026-10-21 14:42:23 +00:00

Member

Copy Link

Copy Source

Member of the delivery group feat/files-through-the-store with mesh-catalog's F3 pull request (design 60, ADR 0468): the controller moves its mesh-sdk pin to d4deecdb (main's merge of mesh-sdk #63, holding main's container-groups pin 85b5a26), whose node-files contract names upload and download. A holder must serve every verb its seat declares, so this controller and the catalogue's mesh-files that serves them merge and are delivered together (ADR 0418); neither passes alone.

History: 227c86eb was refused (no clean merge after main took issue 1638's pin); bb31f6bc's check on g14 passed every unit and integration test but its store tests' go test exited 1 with no reason shown (issue 1740) and no verdict reached the delivery; 550cf37d merges main d96c9f56 (issue 1669) for a fresh check.

Test: TestAFilesHolderServingUploadAndDownloadCanHoldTheSeat (1718/AC2), failing on the old pin. Re-captured testdata/beside/CAPTURED.

Reviewed-by: review-fts@shanks at 550cf37d71

Member of the delivery group feat/files-through-the-store with mesh-catalog's F3 pull request (design 60, ADR 0468): the controller moves its mesh-sdk pin to d4deecdb (main's merge of mesh-sdk #63, holding main's container-groups pin 85b5a26), whose node-files contract names upload and download. A holder must serve every verb its seat declares, so this controller and the catalogue's mesh-files that serves them merge and are delivered together (ADR 0418); neither passes alone. History: 227c86eb was refused (no clean merge after main took issue 1638's pin); bb31f6bc's check on g14 passed every unit and integration test but its store tests' go test exited 1 with no reason shown (issue 1740) and no verdict reached the delivery; 550cf37d merges main d96c9f56 (issue 1669) for a fresh check. Test: TestAFilesHolderServingUploadAndDownloadCanHoldTheSeat (1718/AC2), failing on the old pin. Re-captured testdata/beside/CAPTURED. Reviewed-by: review-fts@shanks at 550cf37d710946ceb7b922eb2bbb00025ec1a3bc

mesh-tools added 1 commit 2026-10-21 14:42:23 +00:00

Take mesh-sdk 90b20f5, so node-files' contract names upload and download (issue 1718) 227c86ebb3

mesh-tools commented 2026-10-21 14:42:50 +00:00

Author

Member

Copy Link

Copy Source

Delivery novox/mesh-controller@550cf37d7109 — superseded since 2026-10-21T16:51:19Z

Delivery plan — builds build-agent, mesh-controller, route-proxy → ace, g14, novox, shanks; no bus step

• tier 0: mesh-controller, route-proxy
• tier 1: build-agent
• ace: receives route-proxy, build-agent
• g14: receives build-agent
• novox: receives mesh-controller, route-proxy, build-agent
• shanks: receives build-agent
• route-proxy provides route: its consumers are sent again after it
• route-proxy keeps data (ADR 0233): what it holds is backed up before it moves
• build-agent keeps data (ADR 0233): what it holds is backed up before it moves
• grants step: if this changes what the bus's user list says (a new tool, subject or user), novox is sent that list alone, every build there kept, before route-proxy, build-agent is judged on its first machine

Group feat/files-through-the-store: novox/mesh-catalog@6cf51173d5, novox/mesh-controller@550cf37d71

• composed together: pass — every machine composes with the change as it did without (4 of 4 compose)

Transitions

• 2026-10-21 15:50 (new) → proposed (announced): novox/mesh-controller#424's head announced
• 2026-10-21 15:59 proposed → checked (checked): a verdict names this commit and the trunk's head as its trunk commit
• 2026-10-21 15:59 checked → ready (accepted): the gate passed or warned, and the repository's own check did not fail
• 2026-10-21 16:51 ready → published (merged): on the trunk its modules follow: merged there, and its walk opened — or nothing for a walk to move
• 2026-10-21 16:51 published → delivering (go): its walk started: let go by this owner in its group's order, by a person, or on the controller's own path — not a failed walk that carried a later commit for it, after which it waits for a walk of its own commit
• 2026-10-21 16:51 delivering → superseded (superseded): its walk was superseded and names no walk that took it over: a walk that took it over answers its merge, and it follows that walk (novox/hq ADR 0276)

The commit's note under refs/notes/mesh-plan keeps every transition: git log --notes=mesh-plan.

<!-- mesh-delivery:view --> **Delivery** `novox/mesh-controller@550cf37d7109` — **superseded** since 2026-10-21T16:51:19Z **Delivery plan** — builds build-agent, mesh-controller, route-proxy → ace, g14, novox, shanks; no bus step - tier 0: mesh-controller, route-proxy - tier 1: build-agent - ace: receives route-proxy, build-agent - g14: receives build-agent - novox: receives mesh-controller, route-proxy, build-agent - shanks: receives build-agent - route-proxy provides route: its consumers are sent again after it - route-proxy keeps data (ADR 0233): what it holds is backed up before it moves - build-agent keeps data (ADR 0233): what it holds is backed up before it moves - grants step: if this changes what the bus's user list says (a new tool, subject or user), novox is sent that list alone, every build there kept, before route-proxy, build-agent is judged on its first machine **Group** `feat/files-through-the-store`: novox/mesh-catalog@6cf51173d586, novox/mesh-controller@550cf37d7109 - composed together: pass — every machine composes with the change as it did without (4 of 4 compose) **Transitions** - 2026-10-21 15:50 (new) → proposed (announced): novox/mesh-controller#424's head announced - 2026-10-21 15:59 proposed → checked (checked): a verdict names this commit and the trunk's head as its trunk commit - 2026-10-21 15:59 checked → ready (accepted): the gate passed or warned, and the repository's own check did not fail - 2026-10-21 16:51 ready → published (merged): on the trunk its modules follow: merged there, and its walk opened — or nothing for a walk to move - 2026-10-21 16:51 published → delivering (go): its walk started: let go by this owner in its group's order, by a person, or on the controller's own path — not a failed walk that carried a later commit for it, after which it waits for a walk of its own commit - 2026-10-21 16:51 delivering → superseded (superseded): its walk was superseded and names no walk that took it over: a walk that took it over answers its merge, and it follows that walk (novox/hq ADR 0276) The commit's note under `refs/notes/mesh-plan` keeps every transition: `git log --notes=mesh-plan`.

mesh-tools referenced this pull request from novox/mesh-catalog 2026-10-21 14:52:59 +00:00

Files go through the store: object-store links, node-files upload/download, a document converter, and brother printing a key, a path on any machine or a web link (design 60 F3, ADR 0468) #417

mesh-tools commented 2026-10-21 14:56:02 +00:00

Author

Member

Copy Link

Copy Source

Merge check at 227c86eb
Judged: head 227c86ebb388 merged into trunk 12752911b644

• mesh/merge-gate: FAIL — head 227c86ebb3 does not merge cleanly into trunk 12752911b6: in conflict go.mod, go.sum, testdata/beside/CAPTURED, vendor/modules.txt
• mesh/repo-check: FAIL — head 227c86ebb3 does not merge cleanly into trunk 12752911b6: in conflict go.mod, go.sum, testdata/beside/CAPTURED, vendor/modules.txt

Delivery plan — builds build-agent, mesh-controller, route-proxy → ace, g14, novox, shanks; no bus step

• tier 0: mesh-controller, route-proxy
• tier 1: build-agent
• ace: receives route-proxy, build-agent
• g14: receives build-agent
• novox: receives mesh-controller, route-proxy, build-agent
• shanks: receives build-agent
• route-proxy provides route: its consumers are sent again after it
• route-proxy keeps data (ADR 0233): what it holds is backed up before it moves
• build-agent keeps data (ADR 0233): what it holds is backed up before it moves
• grants step: if this changes what the bus's user list says (a new tool, subject or user), novox is sent that list alone, every build there kept, before route-proxy, build-agent is judged on its first machine
• read by no module's build: cmd/mesh-controller/seats_test.go, testdata/beside/CAPTURED

Run by the build seat on g14 as build-1792593803626297372 (builds --log build-1792593803626297372).

head 227c86ebb388 does not merge cleanly into trunk 12752911b644: in conflict go.mod, go.sum, testdata/beside/CAPTURED, vendor/modules.txt

**Merge check** at `227c86eb` Judged: head `227c86ebb388` merged into trunk `12752911b644` - `mesh/merge-gate`: **FAIL** — head 227c86ebb388 does not merge cleanly into trunk 12752911b644: in conflict go.mod, go.sum, testdata/beside/CAPTURED, vendor/modules.txt - `mesh/repo-check`: **FAIL** — head 227c86ebb388 does not merge cleanly into trunk 12752911b644: in conflict go.mod, go.sum, testdata/beside/CAPTURED, vendor/modules.txt **Delivery plan** — builds build-agent, mesh-controller, route-proxy → ace, g14, novox, shanks; no bus step - tier 0: mesh-controller, route-proxy - tier 1: build-agent - ace: receives route-proxy, build-agent - g14: receives build-agent - novox: receives mesh-controller, route-proxy, build-agent - shanks: receives build-agent - route-proxy provides route: its consumers are sent again after it - route-proxy keeps data (ADR 0233): what it holds is backed up before it moves - build-agent keeps data (ADR 0233): what it holds is backed up before it moves - grants step: if this changes what the bus's user list says (a new tool, subject or user), novox is sent that list alone, every build there kept, before route-proxy, build-agent is judged on its first machine - read by no module's build: cmd/mesh-controller/seats_test.go, testdata/beside/CAPTURED Run by the build seat on g14 as `build-1792593803626297372` (`builds --log build-1792593803626297372`). ``` head 227c86ebb388 does not merge cleanly into trunk 12752911b644: in conflict go.mod, go.sum, testdata/beside/CAPTURED, vendor/modules.txt ```

jschoubben added 1 commit 2026-10-21 14:57:33 +00:00

Take mesh-sdk d4deecdb, main's merge of node-files' upload and download, over main's container-groups pin (issue 1718) bb31f6bc49

jschoubben added 1 commit 2026-10-21 15:49:59 +00:00

Merge remote-tracking branch 'origin/main' into feat/files-through-the-store-files-verbs 550cf37d71

mesh-tools merged commit d568d76b97 into main 2026-10-21 16:31:28 +00:00

mesh-tools deleted branch feat/files-through-the-store 2026-10-21 16:31:28 +00:00

Sign in to join this conversation.

Reviewers

No Reviewers

Labels

Clear labels

mesh/ready

Reviewed and ready: mesh-delivery merges at the marked head once its checks pass (hq ADR 0364)

No labels

Milestone

No items

No Milestone

Assignees

Clear assignees

agent-ace agent-g14 agent-novox agent-shanks jschoubben mesh-tools miel.truyen nox-agent

No Assignees

2 Participants

Notifications

Subscribe

Due Date

No due date set.

Dependencies

No dependencies set.

Reference: novox/mesh-controller#424