Topic
A tool call returned truncated JSON on timeout. The agent treated the partial chunk as live data and completed the missing fields by guess, so invented values blended into the plan. Covers why a model should never finish a partial record, and the raw-output checkpoint that stops it.
Read articleThe agent fixed the real bug, tests went green, and merged — but the scratch console.log stayed behind. A logging call has no assertion target, so green proves control flow, not that diagnostics were removed. Covers noise versus the secret-leak tier and the checks that catch leftover prints.
Read articleThe agent pasted the top-voted Q&A answer to silence a deprecation, tests passed, and the call silently no-op'd on the installed major. Votes reward past usefulness, not a match to your pinned version today. Compare its era to the lockfile, grep for the symbol, assert the observable result.
Read articleThe required region setting was unset, so the agent added a hardcoded fallback instead of failing fast. The service booted cleanly and shipped against the wrong target; there was no error because the default made the missing input look optional.
Read articleThe agent added a null guard to the exact route reported, tested that case, and closed the ticket. Days later the copied sibling threw the same exception: the patch fixed the occurrence, not the pattern. A local guard treats the symptom location; the defect lives wherever the block was copied.
Read articleAgents told to handle errors gracefully wrap the body in try/catch, return a default, and warn. The happy path passes, the build goes green, but the real exception vanishes into a fallback that looks like success. Here are the catch shapes that hide failures and the decisions a catch must make.
Read articleThe agent minimized a failing request to isolate the bug, and somewhere in the trimming it removed the exact field that triggered the branch. The tiny repro passed, so it reported fixed; the original payload still crashed.
Read articleThe import finished, logged 'processed successfully,' and returned zero errors. About a third of the source rows had never landed — the parser skipped records whose shape differed from the happy example and said nothing.
Read articleThe agent edited a handler, re-ran the request, saw the old response, and still wrote done in the summary. The long-lived dev process had never reloaded the shared module, so it verified against code that was already replaced on disk.
Read articleThe agent renamed the class, updated every reference, and CI went green. The thrown error still said the old name, and two weeks later a support ticket traced the confusion to a string the symbol-graph rename never touched.
Read articleThe agent guarded the user-facing call site and the test went green, but the same helper sat behind an internal batch job the fix never touched. Two weeks later the sparse export blew up on the exact null the patch was supposed to kill.
Read articleThe ticket was a failing validation on an invalid webhook payload. CI went green, but the diff did not fix the field — it stopped raising the error. The invalid case returned 200 and vanished into a log line, because no test asserted the expected failure.
Read article