Issues 239–242: a name taken over, a dry run recorded, every database dropped, no backups #83

Merged
jschoubben merged 3 commits from issues/239-242 into main 2026-10-05 00:25:51 +00:00
Owner
  • 239 a module name is taken over by another repository and nothing refuses it.
  • 240 a dry-run build is recorded and its definition reaches the machine.
  • 238 diagnosis: the operator banned by the forge jail.
  • 241 one unreadable grants file dropped every database on the control node — cause, fixes (mesh-sdk#7 / 0.1.10, mesh-catalog#44, mesh-host#22), recovery and what it lost.
  • 242 the mesh has no backups — what, how often, full vs delta, where, who, how proven.

The earlier PR for 239/240 was lost with the forge's records; its branch is the base of this one. records/index/cycle pass.

- **239** a module name is taken over by another repository and nothing refuses it. - **240** a dry-run build is recorded and its definition reaches the machine. - **238** diagnosis: the operator banned by the forge jail. - **241** one unreadable grants file dropped every database on the control node — cause, fixes (mesh-sdk#7 / 0.1.10, mesh-catalog#44, mesh-host#22), recovery and what it lost. - **242** the mesh has no backups — what, how often, full vs delta, where, who, how proven. The earlier PR for 239/240 was lost with the forge's records; its branch is the base of this one. records/index/cycle pass.
jschoubben added 2 commits 2026-10-05 00:24:13 +00:00
239: two repositories defined photos; a rebuild to the catalogue's main replaced the app with a stub
and nothing refused it. 240: a dry-run build was recorded and its definition reached the machine.
238: the forge refused three ssh logins as the operator's account in 31 seconds; nothing in the mesh's
ssh configuration names the forge, and no jail ignores the mesh's own public addresses.
241: the SDK harness read a failed read as "no consumer" and withdrew all seven databases on the
control node; withdrawal destroyed data in seven providers. Fixed in mesh-sdk 0.1.10, mesh-catalog#44
and mesh-host#22; the recovery and what it lost are recorded. 242: nothing backs anything up.
jschoubben added 1 commit 2026-10-05 00:24:29 +00:00
jschoubben merged commit 2a501af0eb into main 2026-10-05 00:25:51 +00:00
jschoubben deleted branch issues/239-242 2026-10-05 00:25:51 +00:00
Contributor

Delivery novox/hq@2a501af0ebb9 — 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#83 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.

<!-- mesh-delivery:view --> **Delivery** `novox/hq@2a501af0ebb9` — **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#83 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`.
Sign in to join this conversation.
No Reviewers
2 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: novox/hq#83