Opens issue 276 (status located): a media server module's download handler threw after its rescan, because it read an empty 200 body as JSON. Each finished download was then offered five times and raised a false max-deliveries. The runtime's log line also made the handler's error look like the runtime's own.
The issue records the one rule for taking an event: return to take it, throw to have it offered again, and any non-error answer counts as taken. It also records the diagnosis trail, a sweep of every other consumer, and where the fixes are: novox/mesh-media-catalog#5, the mesh-tools PR and mesh-sdk 0.1.13. fixed-by gets filled in when those merge.
records.py, index.py and cycle.py pass. Role names only.
Opens issue 276 (status `located`): a media server module's download handler threw after its rescan, because it read an empty 200 body as JSON. Each finished download was then offered five times and raised a false `max-deliveries`. The runtime's log line also made the handler's error look like the runtime's own.
The issue records the one rule for taking an event: return to take it, throw to have it offered again, and any non-error answer counts as taken. It also records the diagnosis trail, a sweep of every other consumer, and where the fixes are: novox/mesh-media-catalog#5, the mesh-tools PR and mesh-sdk 0.1.13. `fixed-by` gets filled in when those merge.
`records.py`, `index.py` and `cycle.py` pass. Role names only.
A refresh answered with an empty body was read as JSON, so the media server module's handler threw after scanning; each finished download was offered five times and raised a false max-deliveries. Records the one rule for taking an event, and where the fixes are.
Deliverynovox/hq@40e7911da296 — 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#143 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@40e7911da296` — **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#143 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.
Opens issue 276 (status
located): a media server module's download handler threw after its rescan, because it read an empty 200 body as JSON. Each finished download was then offered five times and raised a falsemax-deliveries. The runtime's log line also made the handler's error look like the runtime's own.The issue records the one rule for taking an event: return to take it, throw to have it offered again, and any non-error answer counts as taken. It also records the diagnosis trail, a sweep of every other consumer, and where the fixes are: novox/mesh-media-catalog#5, the mesh-tools PR and mesh-sdk 0.1.13.
fixed-bygets filled in when those merge.records.py,index.pyandcycle.pypass. Role names only.Delivery
novox/hq@40e7911da296— 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 nothing: the change touches no module of the mesh's graph
Transitions
The commit's note under
refs/notes/mesh-plankeeps every transition:git log --notes=mesh-plan.