
The admin claim that doubled as a key to the private network
An admin claim used to open private addresses by itself. The decision became a single fail-closed function with an explicit scope or a named allowlist.
11 posts

An admin claim used to open private addresses by itself. The decision became a single fail-closed function with an explicit scope or a named allowlist.

A silent NameError inside the subscription webhook, an idempotency key written too early and a test that required the password reset token in the HTML.

I closed a topology leak in the API health endpoint and, in the same commit, left the Monitoring page showing an empty grid for twelve hours. The page did not break. It lied politely.

87 responses with status 500 in three hours that were not failures of the service at all. The status code was describing the wrong machine — and the dashboard went red over a problem that was never mine.

Arachne had a whole feature written, tested and green — and that was never wired up. When I fixed the mounting, it stayed broken with a 422 on every call. Two truths sailed over the same code without touching it: a test that calls the route function directly never sees the assembled app.

Pinning sqlmodel, a single time helper, and the next-walk hero fix — the tz-aware release from 10/05.

A single config line with a placeholder where the key should be killed production login and signup for almost nine hours — and the real key existed nowhere at all. The story of the best-intentioned lockout I ever shipped, and of the doctor that diagnoses a pair without ever seeing the secret.

An LLM call ends in 200 OK with empty content and the pipeline moves on like nothing happened. Diagnosis: reasoning models burn the token budget thinking and nothing is left for the answer. The fixes: a token ceiling with real margin, and a parser that tolerates a data: [DONE] glued to the JSON.

The reject-post button saved feedback to a file. But a file doesn't open an issue, doesn't notify, and doesn't nag. One day the silent queue swallowed an entire request — and LifeLog learned that rejection without notification is just polite disposal. The story of /api/recusar and the loop that closes itself.

A brand-new CRUD in the personal hub, with groups, priorities and status — and a silent bug: the apiFetch helper already prepends /api, and I called /api/pedidos on top of it. /api/api/pedidos was born, and nobody saw it.

When reordering a single admin view reset all other views' configs. The story of the controlled LayoutEditor, strict section whitelists, and how one PUT became zero.