Issue 279: a folder cannot be owned by the account a module runs as #151

2026-10-06T18:57:49Z

mesh-admin commented

2026-10-06 18:57:49 +00:00

Opened at the operator's request after the media managers' recycle bins failed on the home server (mesh-media-catalog PR #9; stopgap PR #10, mode 0777).

The problem: the mesh knows one account per node, the operator's (ADR 0181). The account a containerised module runs as is a puid/pgid number on its assignment. A directory's owner can't follow it, because a manifest's owner is literal and ${setting:…} isn't filled there. To-be 29 leaves "one account or several per node" open, while the home server has run media apps as a second account for years.

Also recorded: one module's failed step failed every gate in the rollout on that node, and a rollback with nothing kept was judged a failed rollback.

The report ends with open questions; diagnosis is a separate step. records.py, index.py and cycle.py pass.

Opened at the operator's request after the media managers' recycle bins failed on the home server (mesh-media-catalog PR #9; stopgap PR #10, mode 0777). **The problem:** the mesh knows one account per node, the operator's (ADR 0181). The account a containerised module runs as is a `puid`/`pgid` number on its assignment. A directory's owner can't follow it, because a manifest's owner is literal and `${setting:…}` isn't filled there. To-be 29 leaves "one account or several per node" open, while the home server has run media apps as a second account for years. **Also recorded:** one module's failed step failed every gate in the rollout on that node, and a rollback with nothing kept was judged a failed rollback. The report ends with open questions; diagnosis is a separate step. `records.py`, `index.py` and `cycle.py` pass.

mesh-admin added 1 commit 2026-10-06 18:57:49 +00:00

Issue 279: a folder cannot be owned by the account a module runs as 5e2b520307

mesh-admin merged commit 163b4f6c48 into main

2026-10-06 19:28:47 +00:00

mesh-admin deleted branch issues/279-a-folder-cannot-be-owned-by-the-account-a-module-runs-as

2026-10-06 19:28:47 +00:00

mesh-admin commented

2026-10-06 23:06:55 +00:00

Delivery novox/hq@163b4f6c48ae — held since 2026-10-06T23:05:28Z

Held for a person: merged without a passing check: only a person decides that it goes on — mesh-delivery.release with why lets it go on.

Delivery plan — builds nothing: the change touches no module of the mesh's graph

Transitions

2026-10-06 23:05 (new) → proposed (announced): novox/hq#151 merged; its head was not heard by this owner, so it is made from the forge's word
2026-10-06 23:05 proposed → held (merged-unchecked): merged without a passing check — a verdict known with it is taken first: only a person decides that it goes on

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

**Delivery** `novox/hq@163b4f6c48ae` — **held** since 2026-10-06T23:05:28Z Held for a person: merged without a passing check: only a person decides that it goes on — `mesh-delivery.release` with why lets it go on. **Delivery plan** — builds nothing: the change touches no module of the mesh's graph **Transitions** - 2026-10-06 23:05 (new) → proposed (announced): novox/hq#151 merged; its head was not heard by this owner, so it is made from the forge's word - 2026-10-06 23:05 proposed → held (merged-unchecked): merged without a passing check — a verdict known with it is taken first: only a person decides that it goes on The commit's note under `refs/notes/mesh-plan` keeps every transition: `git log --notes=mesh-plan`.

jschoubben referenced this issue from a commit

2026-10-09 01:24:12 +00:00

ADR 0270: how a failed new-module build is said, a one-machine module is never covered, and which gate tests the forge module

Sign in to join this conversation.

1 Participants

Notifications

Due Date

No due date set.

Dependencies

No dependencies set.

Reference: novox/hq#151