novox/photos
9
0
Fork 0
Code Issues 2 Pull Requests 1 Releases Wiki Activity

Feature 57 (config and provisioning): release photos #5

Merged
mesh-tools merged 1 commits from release/57-config-and-provisioning into nox-mesh 2026-10-16 13:04:21 +00:00
Conversation 5 Commits 1 Files Changed 4
+37 -2
mesh-tools commented 2026-10-16 09:44:34 +00:00
Member
Copy Link
Copy Source

Feature 57's photos part (env files' text in files/ as templates, reviewed at 990b762) as one commit on top of nox-mesh 31c0c5e6: tree 66c0b0ef. Delivery group bundle B.

Feature 57's photos part (env files' text in files/ as templates, reviewed at 990b762) as one commit on top of nox-mesh 31c0c5e6: tree 66c0b0ef. Delivery group bundle B.
mesh-tools added 1 commit 2026-10-16 09:44:34 +00:00
Keep the photo application's env files' text in files/, as templates (feature 57), reviewed
mesh/merge-gate head aaf6fe4d53d7 merged into trunk 31c0c5e6bcad — pass: builds photos, sent nowhere; no bus step; 1 wait(s) for a person; every machine co…
Details
mesh/repo-check head aaf6fe4d53d7 merged into trunk 31c0c5e6bcad — pass: THE CHANGE ALTERS ITS OWN CHECK (merge-check.sh): nox-mesh's version judged it; th…
Details
mesh/delivery delivered
Details
aaf6fe4d53
mesh-tools commented 2026-10-16 09:45:02 +00:00
Author
Member
Copy Link
Copy Source

Delivery novox/photos@aaf6fe4d53d7 — delivered since 2026-10-16T13:08:38Z

Delivery plan — builds photos, sent nowhere; no bus step; 1 wait(s) for a person

  • tier 0: photos
  • novox: waits for a person: photos
  • photos waits for a person: its policy records (irreplaceable data) — unless on a machine its move recreates none of its containers and moves none of its data, which the walk judges and then sends
  • photos keeps data (ADR 0233): what it holds is backed up before it moves

Transitions

  • 2026-10-16 09:44 (new) → proposed (announced): novox/photos#5's head announced
  • 2026-10-16 09:51 proposed → checked (checked): a verdict names this commit and the trunk's head as its trunk commit
  • 2026-10-16 09:51 checked → rejected (refused): the gate failed or could not run, or the repository's own check failed
  • 2026-10-16 09:55 rejected → proposed (recheck): the check could not run: its throwaway store never became ready; checked again to read the store's own log while it runs
  • 2026-10-16 09:59 proposed → checked (checked): a verdict names this commit and the trunk's head as its trunk commit
  • 2026-10-16 09:59 checked → rejected (refused): the gate failed or could not run, or the repository's own check failed
  • 2026-10-16 12:45 rejected → proposed (recheck): feature 57 bundle B: the 09:59 check could not run (build store never became ready); judge it again before merging
  • 2026-10-16 12:53 proposed → checked (checked): a verdict names this commit and the trunk's head as its trunk commit
  • 2026-10-16 12:53 checked → ready (accepted): the gate passed or warned, and the repository's own check did not fail
  • 2026-10-16 13:04 ready → published (merged): on the trunk its modules follow: merged there, and its walk opened — or nothing for a walk to move
  • 2026-10-16 13:04 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-16 13:08 delivering → delivered (done): its walk is done, carrying its own commit: every machine of its deploy plan passed, or was left as its policy says

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

<!-- mesh-delivery:view --> **Delivery** `novox/photos@aaf6fe4d53d7` — **delivered** since 2026-10-16T13:08:38Z **Delivery plan** — builds photos, sent nowhere; no bus step; 1 wait(s) for a person - tier 0: photos - novox: waits for a person: photos - photos waits for a person: its policy records (irreplaceable data) — unless on a machine its move recreates none of its containers and moves none of its data, which the walk judges and then sends - photos keeps data (ADR 0233): what it holds is backed up before it moves **Transitions** - 2026-10-16 09:44 (new) → proposed (announced): novox/photos#5's head announced - 2026-10-16 09:51 proposed → checked (checked): a verdict names this commit and the trunk's head as its trunk commit - 2026-10-16 09:51 checked → rejected (refused): the gate failed or could not run, or the repository's own check failed - 2026-10-16 09:55 rejected → proposed (recheck): the check could not run: its throwaway store never became ready; checked again to read the store's own log while it runs - 2026-10-16 09:59 proposed → checked (checked): a verdict names this commit and the trunk's head as its trunk commit - 2026-10-16 09:59 checked → rejected (refused): the gate failed or could not run, or the repository's own check failed - 2026-10-16 12:45 rejected → proposed (recheck): feature 57 bundle B: the 09:59 check could not run (build store never became ready); judge it again before merging - 2026-10-16 12:53 proposed → checked (checked): a verdict names this commit and the trunk's head as its trunk commit - 2026-10-16 12:53 checked → ready (accepted): the gate passed or warned, and the repository's own check did not fail - 2026-10-16 13:04 ready → published (merged): on the trunk its modules follow: merged there, and its walk opened — or nothing for a walk to move - 2026-10-16 13:04 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-16 13:08 delivering → delivered (done): its walk is done, carrying its own commit: every machine of its deploy plan passed, or was left as its policy says The commit's note under `refs/notes/mesh-plan` keeps every transition: `git log --notes=mesh-plan`.
mesh-tools commented 2026-10-16 09:51:42 +00:00
Author
Member
Copy Link
Copy Source

Merge check at aaf6fe4d

  • mesh/merge-gate: ERROR — the check could not run: build-1792144062102979355-store never became ready (modules: photos)
  • mesh/repo-check: ERROR — the check could not run: build-1792144062102979355-store never became ready

Delivery plan — builds photos, sent nowhere; no bus step; 1 wait(s) for a person

  • tier 0: photos
  • novox: waits for a person: photos
  • photos waits for a person: its policy records (irreplaceable data) — unless on a machine its move recreates none of its containers and moves none of its data, which the walk judges and then sends
  • photos keeps data (ADR 0233): what it holds is backed up before it moves

Run by the build seat on novox as build-1792144062102979355 (builds --log build-1792144062102979355).

**Merge check** at `aaf6fe4d` - `mesh/merge-gate`: **ERROR** — the check could not run: build-1792144062102979355-store never became ready (modules: photos) - `mesh/repo-check`: **ERROR** — the check could not run: build-1792144062102979355-store never became ready **Delivery plan** — builds photos, sent nowhere; no bus step; 1 wait(s) for a person - tier 0: photos - novox: waits for a person: photos - photos waits for a person: its policy records (irreplaceable data) — unless on a machine its move recreates none of its containers and moves none of its data, which the walk judges and then sends - photos keeps data (ADR 0233): what it holds is backed up before it moves Run by the build seat on novox as `build-1792144062102979355` (`builds --log build-1792144062102979355`).
mesh-tools commented 2026-10-16 09:59:24 +00:00
Author
Member
Copy Link
Copy Source

Merge check at aaf6fe4d

  • mesh/merge-gate: ERROR — the check could not run: build-1792144508505999432-store never became ready (modules: photos)
  • mesh/repo-check: ERROR — the check could not run: build-1792144508505999432-store never became ready

Delivery plan — builds photos, sent nowhere; no bus step; 1 wait(s) for a person

  • tier 0: photos
  • novox: waits for a person: photos
  • photos waits for a person: its policy records (irreplaceable data) — unless on a machine its move recreates none of its containers and moves none of its data, which the walk judges and then sends
  • photos keeps data (ADR 0233): what it holds is backed up before it moves

Run by the build seat on novox as build-1792144508505999432 (builds --log build-1792144508505999432).

**Merge check** at `aaf6fe4d` - `mesh/merge-gate`: **ERROR** — the check could not run: build-1792144508505999432-store never became ready (modules: photos) - `mesh/repo-check`: **ERROR** — the check could not run: build-1792144508505999432-store never became ready **Delivery plan** — builds photos, sent nowhere; no bus step; 1 wait(s) for a person - tier 0: photos - novox: waits for a person: photos - photos waits for a person: its policy records (irreplaceable data) — unless on a machine its move recreates none of its containers and moves none of its data, which the walk judges and then sends - photos keeps data (ADR 0233): what it holds is backed up before it moves Run by the build seat on novox as `build-1792144508505999432` (`builds --log build-1792144508505999432`).
mesh-tools commented 2026-10-16 13:02:55 +00:00
Author
Member
Copy Link
Copy Source

Merge check at aaf6fe4d
Judged: head aaf6fe4d53d7 merged into trunk 31c0c5e6bcad; read beside it: mesh-catalog 3db85a0dde83, mesh-controller a20680dfe769, mesh-controller-main a20680dfe769, mesh-host cd13f7726ef0, mesh-tools 7412c5b6c9c5

  • mesh/merge-gate: PASS — every machine composes with the change as it did without (4 of 4 compose) (modules: photos)
  • mesh/repo-check: PASS — THE CHANGE ALTERS ITS OWN CHECK (merge-check.sh): nox-mesh's version judged it; the change's judges the pull requests after it merges; its merge-check.sh passed

Delivery plan — builds photos, sent nowhere; no bus step; 1 wait(s) for a person

  • tier 0: photos
  • novox: waits for a person: photos
  • photos waits for a person: its policy records (irreplaceable data) — unless on a machine its move recreates none of its containers and moves none of its data, which the walk judges and then sends
  • photos keeps data (ADR 0233): what it holds is backed up before it moves

Run by the build seat on ace as build-1792154715710876212 (builds --log build-1792154715710876212).

--- the gate: photos
photos: ok; WARNING: server, admin, eef, filip stay(s) up and say(s) not how it is ready — judged by liveness alone, refused from 2026-11-18 (ADR 0240 rule 8)
long-running resources without health: 4
files asking for a setting without saying whether it is trusted: 0
1 manifest(s) checked. Judged against the seats this binary carries; a claim on one of the mesh's own seats is judged fully at registration, and a seat declared by a module not given here reads as unknown. Identities judged on a 6-character machine name, against the bounds of the providers given here
judging 0 module(s) changed against 4 machine(s), as the snapshot of 2026-10-16T12:40:06Z says they run
composing every machine as the mesh is
the bus's user list leaves out 5 user(s) the mesh has minted no credential for: controller, node.f35, node.idt, node.ygcyr, node.yvbpsm. Each is a user that cannot connect until one is issued
the bus's user list leaves out 5 user(s) the mesh has minted no credential for: controller, node.f35, node.idt, node.ygcyr, node.yvbpsm. Each is a user that cannot connect until one is issued
composing every machine with the change
the bus's user list leaves out 5 user(s) the mesh has minted no credential for: controller, node.f35, node.idt, node.ygcyr, node.yvbpsm. Each is a user that cannot connect until one is issued
the bus's user list leaves out 5 user(s) the mesh has minted no credential for: controller, node.f35, node.idt, node.ygcyr, node.yvbpsm. Each is a user that cannot connect until one is issued
merge gate: PASS — every machine composes with the change as it did without (4 of 4 compose)
judged by controller development build against the facts of 2026-10-16T12:40:06Z

machines:
  - a machine (f35): composes
  - holds mesh-dns-resolver (idt): composes
  - holds git, holds mesh-artifact-store, holds mesh-broker, holds mesh-catalog, holds mesh-delivery, holds mesh-dns-resolver, holds mesh-store, holds mesh-vault, holds npm-package-registry, the control node, the hub (ygcyr): composes
  - a machine (yvbpsm): composes

a merge would rebuild 1 module(s) in 1 tier(s): photos
--- THE CHANGE ALTERS ITS OWN CHECK (merge-check.sh): nox-mesh's version judged it; the change's judges the pull requests after it merges
--- its merge-check.sh (typescript toolchain)
--- server: installed from its lock file and built

added 275 packages in 2s

> photos-api@1.0.0 build
> rollup --config


src/server.js → dist/server.mjs, dist/server.cjs...
(!) Circular dependencies
node_modules/mongodb/lib/change_stream.js -> node_modules/mongodb/lib/collection.js -> node_modules/mongodb/lib/change_stream.js
node_modules/mongodb/lib/collection.js -> node_modules/mongodb/lib/operations/rename.js -> node_modules/mongodb/lib/collection.js
node_modules/mongodb/lib/change_stream.js -> node_modules/mongodb/lib/cursor/change_stream_cursor.js -> node_modules/mongodb/lib/change_stream.js
...and 63 more
(!) Plugin node-resolve: preferring built-in module 'util' over local alternative at '/var/lib/build-agent/workspace/check/photos/server/node_modules/util/util.js', pass 'preferBuiltins: false' to disable this behavior or 'preferBuiltins: true' to disable this warning
(!) Plugin node-resolve: preferring built-in module 'string_decoder' over local alternative at '/var/lib/build-agent/workspace/check/photos/server/node_modules/string_decoder/lib/string_decoder.js', pass 'preferBuiltins: false' to disable this behavior or 'preferBuiltins: true' to disable this warning
(!) Use of eval is strongly discouraged
https://rollupjs.org/troubleshooting/#avoiding-eval
node_modules/koa/node_modules/http-errors/node_modules/depd/index.js
408: 
409:    // eslint-disable-next-line no-eval
410:   var deprecatedfn = eval('(function (' + args + ') {\n' +
                          ^
411:     '"use strict"\n' +
412:     'log.call(deprecate, message, site)\n' +
node_modules/http-assert/node_modules/depd/index.js
408: 
409:    // eslint-disable-next-line no-eval
410:   var deprecatedfn = eval('(function (' + args + ') {\n' +
                          ^
411:     '"use strict"\n' +
412:     'log.call(deprecate, message, site)\n' +
created dist/server.mjs, dist/server.cjs in 7.3s
--- client: installed from its lock file and built

added 1521 packages in 8s

> public-app@0.1.0 build
> react-scripts build

Creating an optimized production build...
Browserslist: caniuse-lite is outdated. Please run:
  npx update-browserslist-db@latest
  Why you should do it regularly: https://github.com/browserslist/update-db#readme
Browserslist: caniuse-lite is outdated. Please run:
  npx update-browserslist-db@latest
  Why you should do it regularly: https://github.com/browserslist/update-db#readme
Compiled successfully.

File sizes after gzip:

  75.72 kB  build/static/js/main.061fea96.js
  4.01 kB   build/static/css/main.f2f2debd.css

The project was built assuming it is hosted at /.
You can control this with the homepage field in your package.json.

The build folder is ready to be deployed.
You may serve it with a static server:

  npm install -g serve
  serve -s build

Find out more about deployment here:

  https://cra.link/deployment

--- admin-client: installed from its lock file and built

added 1518 packages in 9s

> admin-app@0.1.0 build
> react-scripts build

Creating an optimized production build...
Browserslist: caniuse-lite is outdated. Please run:
  npx update-browserslist-db@latest
  Why you should do it regularly: https://github.com/browserslist/update-db#readme
Browserslist: caniuse-lite is outdated. Please run:
  npx update-browserslist-db@latest
  Why you should do it regularly: https://github.com/browserslist/update-db#readme
Compiled successfully.

File sizes after gzip:

  140.89 kB  build/static/js/main.7652d819.js
  3.71 kB    build/static/css/main.00ab3e17.css

The project was built assuming it is hosted at /.
You can control this with the homepage field in your package.json.

The build folder is ready to be deployed.
You may serve it with a static server:

  npm install -g serve
  serve -s build

Find out more about deployment here:

  https://cra.link/deployment

NOT RUN HERE: the server (it wants its object and document stores); the application has no tests
**Merge check** at `aaf6fe4d` Judged: head `aaf6fe4d53d7` merged into trunk `31c0c5e6bcad`; read beside it: mesh-catalog `3db85a0dde83`, mesh-controller `a20680dfe769`, mesh-controller-main `a20680dfe769`, mesh-host `cd13f7726ef0`, mesh-tools `7412c5b6c9c5` - `mesh/merge-gate`: **PASS** — every machine composes with the change as it did without (4 of 4 compose) (modules: photos) - `mesh/repo-check`: **PASS** — THE CHANGE ALTERS ITS OWN CHECK (merge-check.sh): nox-mesh's version judged it; the change's judges the pull requests after it merges; its merge-check.sh passed **Delivery plan** — builds photos, sent nowhere; no bus step; 1 wait(s) for a person - tier 0: photos - novox: waits for a person: photos - photos waits for a person: its policy records (irreplaceable data) — unless on a machine its move recreates none of its containers and moves none of its data, which the walk judges and then sends - photos keeps data (ADR 0233): what it holds is backed up before it moves Run by the build seat on ace as `build-1792154715710876212` (`builds --log build-1792154715710876212`). ``` --- the gate: photos photos: ok; WARNING: server, admin, eef, filip stay(s) up and say(s) not how it is ready — judged by liveness alone, refused from 2026-11-18 (ADR 0240 rule 8) long-running resources without health: 4 files asking for a setting without saying whether it is trusted: 0 1 manifest(s) checked. Judged against the seats this binary carries; a claim on one of the mesh's own seats is judged fully at registration, and a seat declared by a module not given here reads as unknown. Identities judged on a 6-character machine name, against the bounds of the providers given here judging 0 module(s) changed against 4 machine(s), as the snapshot of 2026-10-16T12:40:06Z says they run composing every machine as the mesh is the bus's user list leaves out 5 user(s) the mesh has minted no credential for: controller, node.f35, node.idt, node.ygcyr, node.yvbpsm. Each is a user that cannot connect until one is issued the bus's user list leaves out 5 user(s) the mesh has minted no credential for: controller, node.f35, node.idt, node.ygcyr, node.yvbpsm. Each is a user that cannot connect until one is issued composing every machine with the change the bus's user list leaves out 5 user(s) the mesh has minted no credential for: controller, node.f35, node.idt, node.ygcyr, node.yvbpsm. Each is a user that cannot connect until one is issued the bus's user list leaves out 5 user(s) the mesh has minted no credential for: controller, node.f35, node.idt, node.ygcyr, node.yvbpsm. Each is a user that cannot connect until one is issued merge gate: PASS — every machine composes with the change as it did without (4 of 4 compose) judged by controller development build against the facts of 2026-10-16T12:40:06Z machines: - a machine (f35): composes - holds mesh-dns-resolver (idt): composes - holds git, holds mesh-artifact-store, holds mesh-broker, holds mesh-catalog, holds mesh-delivery, holds mesh-dns-resolver, holds mesh-store, holds mesh-vault, holds npm-package-registry, the control node, the hub (ygcyr): composes - a machine (yvbpsm): composes a merge would rebuild 1 module(s) in 1 tier(s): photos --- THE CHANGE ALTERS ITS OWN CHECK (merge-check.sh): nox-mesh's version judged it; the change's judges the pull requests after it merges --- its merge-check.sh (typescript toolchain) --- server: installed from its lock file and built added 275 packages in 2s > photos-api@1.0.0 build > rollup --config  src/server.js → dist/server.mjs, dist/server.cjs... (!) Circular dependencies node_modules/mongodb/lib/change_stream.js -> node_modules/mongodb/lib/collection.js -> node_modules/mongodb/lib/change_stream.js node_modules/mongodb/lib/collection.js -> node_modules/mongodb/lib/operations/rename.js -> node_modules/mongodb/lib/collection.js node_modules/mongodb/lib/change_stream.js -> node_modules/mongodb/lib/cursor/change_stream_cursor.js -> node_modules/mongodb/lib/change_stream.js ...and 63 more (!) Plugin node-resolve: preferring built-in module 'util' over local alternative at '/var/lib/build-agent/workspace/check/photos/server/node_modules/util/util.js', pass 'preferBuiltins: false' to disable this behavior or 'preferBuiltins: true' to disable this warning (!) Plugin node-resolve: preferring built-in module 'string_decoder' over local alternative at '/var/lib/build-agent/workspace/check/photos/server/node_modules/string_decoder/lib/string_decoder.js', pass 'preferBuiltins: false' to disable this behavior or 'preferBuiltins: true' to disable this warning (!) Use of eval is strongly discouraged https://rollupjs.org/troubleshooting/#avoiding-eval node_modules/koa/node_modules/http-errors/node_modules/depd/index.js 408: 409: // eslint-disable-next-line no-eval 410: var deprecatedfn = eval('(function (' + args + ') {\n' + ^ 411: '"use strict"\n' + 412: 'log.call(deprecate, message, site)\n' + node_modules/http-assert/node_modules/depd/index.js 408: 409: // eslint-disable-next-line no-eval 410: var deprecatedfn = eval('(function (' + args + ') {\n' + ^ 411: '"use strict"\n' + 412: 'log.call(deprecate, message, site)\n' + created dist/server.mjs, dist/server.cjs in 7.3s --- client: installed from its lock file and built added 1521 packages in 8s > public-app@0.1.0 build > react-scripts build Creating an optimized production build... Browserslist: caniuse-lite is outdated. Please run: npx update-browserslist-db@latest Why you should do it regularly: https://github.com/browserslist/update-db#readme Browserslist: caniuse-lite is outdated. Please run: npx update-browserslist-db@latest Why you should do it regularly: https://github.com/browserslist/update-db#readme Compiled successfully. File sizes after gzip: 75.72 kB build/static/js/main.061fea96.js 4.01 kB build/static/css/main.f2f2debd.css The project was built assuming it is hosted at /. You can control this with the homepage field in your package.json. The build folder is ready to be deployed. You may serve it with a static server: npm install -g serve serve -s build Find out more about deployment here: https://cra.link/deployment --- admin-client: installed from its lock file and built added 1518 packages in 9s > admin-app@0.1.0 build > react-scripts build Creating an optimized production build... Browserslist: caniuse-lite is outdated. Please run: npx update-browserslist-db@latest Why you should do it regularly: https://github.com/browserslist/update-db#readme Browserslist: caniuse-lite is outdated. Please run: npx update-browserslist-db@latest Why you should do it regularly: https://github.com/browserslist/update-db#readme Compiled successfully. File sizes after gzip: 140.89 kB build/static/js/main.7652d819.js 3.71 kB build/static/css/main.00ab3e17.css The project was built assuming it is hosted at /. You can control this with the homepage field in your package.json. The build folder is ready to be deployed. You may serve it with a static server: npm install -g serve serve -s build Find out more about deployment here: https://cra.link/deployment NOT RUN HERE: the server (it wants its object and document stores); the application has no tests ```
mesh-tools added the mesh/ready label 2026-10-16 13:04:17 +00:00
mesh-tools commented 2026-10-16 13:04:17 +00:00
Author
Member
Copy Link
Copy Source

ready at aaf6fe4d53

ready at aaf6fe4d53d7f1585a5a5a58277552826bf8bd12
mesh-tools merged commit 48a55bef93 into nox-mesh 2026-10-16 13:04:21 +00:00
mesh-tools deleted branch release/57-config-and-provisioning 2026-10-16 13:04:22 +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 mesh/ready
Milestone
No items
No Milestone
Assignees
Clear assignees
agent-ace agent-g14 agent-novox agent-shanks filipv jschoubben mesh-tools miel.truyen nox-agent
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: novox/photos#5