mesh/merge-gate head ee2160d00c22 merged into trunk c71c513027e5 — fail: builds gitea → novox; no bus step; head ee2160d00c22 does not merge cleanly into t…
mesh/repo-check head ee2160d00c22 merged into trunk c71c513027e5 — fail: head ee2160d00c22 does not merge cleanly into trunk c71c513027e5: in conflict modu…
mesh/delivery stopped: the pull request closed unmerged
On 2026-10-14 from 22:28 local the forge held two tokens named mesh-tools. gitea refuses a delete by such a name with 422 "multiple matches", so every gitea tool call re-entered the mint, made two basic-auth calls that hash the admin password, and failed: several times a minute, on a control-node that was already overloaded, and mesh-delivery could read neither open pulls nor views. The watcher and the tools run as separate bundles, so the in-process sharing of one token source does not cover them; two mints racing leave two tokens by the name, because the forge's check that a name is unused is not atomic. A 422 on the delete by name now lists the account's tokens and drops each one carrying the name by its id, then mints. A failed mint is not asked of the forge again for 30 s: the same error is answered without a call.