main is currently failing cycle.py — two records numbered 0201. This fixes it.
The derived-value record is renumbered a second time. The bundles record took 0188 while it waited in a pull request; the key-value-buckets record took 0201 while it waited again. Free when chosen, taken by the time it landed, both times. Mine landed last, so mine moves — and cycle.py is what caught it, which is the check doing exactly its job.
Three issues, each found by watching this go out:
225 — a provisioner cannot read its grant secrets since its code left the container.EACCES on /var/lib/mongodb/grants/*.secret, 4330 times since 01:30:20, so no user is created and two consumers crash-loop with UserNotFound. The files are root-owned from 2026-09-26; the provisioner is now the operator's account, because ADR 0198 moved a module's long-running code under the node runtime. Not from group 8 — that landed two to three hours later and only made a silent fault visible by recreating the containers. The one thing that hid it: the message is secret not readable yet, which is right on the first pass and wrong four thousand times.
226 — the store's sweep stops at the first reference recorded with an address, and so collects nothing of the 1681 it found. Two correct decisions meeting badly: refusing to address an unrecognised reference, and stopping at the first refusal because "a store that refuses one refuses all". A guard that cannot tell I will not ask about this from it would not answer stops the wrong amount of work.
227 — the photo app's admin client asks for port 80, which the reverse proxy holds. Surfaced by rebuilding photos from September to main, which ADR 0202's refusal of its transcribed bucket forced. A module pinned months behind carries everything its branch gained, all at once, the first time anything makes it move.
All three checks pass on this branch.
The matching comment-only renumbers are open and deliberately unmerged — mesh-controller #260, mesh-sdk #21, mesh-catalog #255 — because merging a comment change rebuilds and, for the controller, rolls. Worth riding along with the next real change rather than a wave of their own at this hour.
**main is currently failing `cycle.py`** — two records numbered 0201. This fixes it.
The derived-value record is renumbered a second time. The bundles record took 0188 while it waited in a pull request; the key-value-buckets record took 0201 while it waited again. Free when chosen, taken by the time it landed, both times. Mine landed last, so mine moves — and `cycle.py` is what caught it, which is the check doing exactly its job.
**Three issues, each found by watching this go out:**
- **225 — a provisioner cannot read its grant secrets since its code left the container.** `EACCES` on `/var/lib/mongodb/grants/*.secret`, **4330 times since 01:30:20**, so no user is created and two consumers crash-loop with `UserNotFound`. The files are `root`-owned from 2026-09-26; the provisioner is now the operator's account, because ADR 0198 moved a module's long-running code under the node runtime. **Not from group 8** — that landed two to three hours later and only made a silent fault visible by recreating the containers. The one thing that hid it: the message is `secret not readable yet`, which is right on the first pass and wrong four thousand times.
- **226 — the store's sweep stops at the first reference recorded with an address**, and so collects nothing of the 1681 it found. Two correct decisions meeting badly: refusing to address an unrecognised reference, and stopping at the first refusal because "a store that refuses one refuses all". A guard that cannot tell *I will not ask about this* from *it would not answer* stops the wrong amount of work.
- **227 — the photo app's admin client asks for port 80**, which the reverse proxy holds. Surfaced by rebuilding `photos` from September to main, which ADR 0202's refusal of its transcribed bucket forced. A module pinned months behind carries everything its branch gained, all at once, the first time anything makes it move.
All three checks pass on this branch.
The matching comment-only renumbers are open and **deliberately unmerged** — mesh-controller #260, mesh-sdk #21, mesh-catalog #255 — because merging a comment change rebuilds and, for the controller, rolls. Worth riding along with the next real change rather than a wave of their own at this hour.
The derived-value record is renumbered a second time: the key-value-buckets
record took 0201 while this waited to merge, as the bundles record took 0188
before it. Both times free when chosen, taken by the time it landed. cycle.py
caught it; three repositories cite this record, so the number matters.
225 — a provisioner has not been able to read its grant secrets since 01:30,
when a module's own code left its container and the files stayed root's. Four
thousand refusals, each worded as patience, and two consumers unserved. Not
from ADR 0202 or 0189, which landed hours later; dates in the report.
226 — the store's sweep stops at the first reference recorded with an address
and collects nothing. A guard that cannot tell 'I will not ask about this'
from 'it would not answer' stops the wrong amount of work.
227 — the photo app's admin client asks for the port the proxy holds. A module
pinned months behind carries everything its branch gained, the first time
anything makes it move.
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.
main is currently failing
cycle.py— two records numbered 0201. This fixes it.The derived-value record is renumbered a second time. The bundles record took 0188 while it waited in a pull request; the key-value-buckets record took 0201 while it waited again. Free when chosen, taken by the time it landed, both times. Mine landed last, so mine moves — and
cycle.pyis what caught it, which is the check doing exactly its job.Three issues, each found by watching this go out:
EACCESon/var/lib/mongodb/grants/*.secret, 4330 times since 01:30:20, so no user is created and two consumers crash-loop withUserNotFound. The files areroot-owned from 2026-09-26; the provisioner is now the operator's account, because ADR 0198 moved a module's long-running code under the node runtime. Not from group 8 — that landed two to three hours later and only made a silent fault visible by recreating the containers. The one thing that hid it: the message issecret not readable yet, which is right on the first pass and wrong four thousand times.photosfrom September to main, which ADR 0202's refusal of its transcribed bucket forced. A module pinned months behind carries everything its branch gained, all at once, the first time anything makes it move.All three checks pass on this branch.
The matching comment-only renumbers are open and deliberately unmerged — mesh-controller #260, mesh-sdk #21, mesh-catalog #255 — because merging a comment change rebuilds and, for the controller, rolls. Worth riding along with the next real change rather than a wave of their own at this hour.