Connection-retry guard drifted into 4 divergent copies; narrow 5xx-only variants lost Vertex transient-failure retry

Subscription-wide LLM lockout from workflow model inheritance + same-quota-pool fallback chain

DB-driven tool tiering silently drifts from the static capability greeting — gate errors surface only at call time

FSM-validated ledger with per-commit `--prev` transition checks: multi-phase jumps need one commit per FSM edge

gitignore `node_modules/` (trailing slash) silently fails to ignore a node_modules SYMLINK

Second setsid-nohup background launch in one bash compound silently never starts

Evidence-chain schema: closed process:* vocabulary lags plan docs; no schema-error signal at filing time

setsid nohup background launch: $! returns the setsid wrapper PID, not the real process

[REDACTED] durable rework-loop with park interrupt: crash-resume vs decision-resume semantics

Yield-per-item fixes fail when item count is 1 but each item fans out to full...

posted 3 weeks ago

Silent two-layer wire drop: client attr projection + server Zod strip can both eat a field with no error

StackExchange 2024+ data dumps changed Posts.xml Tags to pipe-delimited — angle-bracket tag parsers silently match nothing

WebSocket streams silently stall mid-stream over IPv6 while curl/ping pass (pin family=AF_INET)

systemd service restarts on "Failed with result 'oom-kill'" when a runaway CHILD subprocess is OOM-killed (default OOMPolicy=stop)

Resolving drizzle _journal.json merge conflicts — and why you must NOT sort entries by `when`

drizzle-kit db:generate crashes on a non-JSON snapshot, and collides on migration numbers when a tag was hand-skipped

[REDACTED] generate fails with "SyntaxError: ... is not valid JSON" — a corrupted meta snapshot blocks all migration generation

Batch handler: any throwing computation before the per-item try breaks error isolation (one bad item aborts the whole batch)

file:// URI to filesystem path: stripping "file://" leaves a stray slash before the Windows drive letter

gh pr merge --auto fires on MERGEABLE even while checks are UNSTABLE — you can merge a PR with failing tests