hq issue 241: on 2026-10-04 one unreadable read of the contributions file made the postgres provider drop every database on the control node. readContributions now returns null for unreadable / not JSON / wrong requirement / no given list; such a pass applies and removes nothing and says why once. Only a read file with a given list withdraws. Every removal is logged before it is made. New test fails on the old harness and passes here; 21/21.
hq issue 241: on 2026-10-04 one unreadable read of the contributions file made the postgres provider drop every database on the control node. readContributions now returns null for unreadable / not JSON / wrong requirement / no given list; such a pass applies and removes nothing and says why once. Only a read file with a given list withdraws. Every removal is logged before it is made. New test fails on the old harness and passes here; 21/21.
An unreadable, unparsable or unrecognised contributions file was read as "no consumer asks", and the
reconcile pass then removed every consumer it had applied. On 2026-10-04 one such read made the
postgres provider drop every database on the control node. Such a pass now applies and removes
nothing and says why, once; only a file read with a given list withdraws a consumer, and every
removal is logged before it is made.
Deliverynovox/mesh-sdk@1e45f1c95a7e — 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 mesh-sdk, sent nowhere; no bus step
tier 0: mesh-sdk
Transitions
2026-10-06 23:05 (new) → proposed (announced): novox/mesh-sdk#7 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/mesh-sdk@1e45f1c95a7e` — **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 mesh-sdk, sent nowhere; no bus step
- tier 0: mesh-sdk
**Transitions**
- 2026-10-06 23:05 (new) → proposed (announced): novox/mesh-sdk#7 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`.
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
hq issue 241: on 2026-10-04 one unreadable read of the contributions file made the postgres provider drop every database on the control node. readContributions now returns null for unreadable / not JSON / wrong requirement / no given list; such a pass applies and removes nothing and says why once. Only a read file with a given list withdraws. Every removal is logged before it is made. New test fails on the old harness and passes here; 21/21.
b1d762624etoa5778390b4Delivery
novox/mesh-sdk@1e45f1c95a7e— held since 2026-10-06T23:05:28ZHeld for a person: merged without a passing check: only a person decides that it goes on —
mesh-delivery.releasewith why lets it go on.Delivery plan — builds mesh-sdk, sent nowhere; no bus step
Transitions
The commit's note under
refs/notes/mesh-plankeeps every transition:git log --notes=mesh-plan.