Codex logging bug may write TBs to local SSDs

Post by applfanboysbgon » Mon, Jun 22, 2026, 8:32 AM UTC

indiv0 wrote: post #14

This thread will become a typical "haha slop company made slop" but I've been bitten by a bug exactly like this before in a (pre-AI, artisan) OSS project. The maintainer there didn't properly account for DST when calculating last backup time, so the app started and never stopped writing/re-writing backups continuously. Perhaps the framing shouldn't be "haha slop" but rather why doesn't the AI write better quality sof…

Post by bob1029 » Mon, Jun 22, 2026, 8:38 AM UTC

Post by HPsquared » Mon, Jun 22, 2026, 8:43 AM UTC

rvz wrote: post #19

The first of many bugs that are beyond the complexity of its authors, thanks to comprehension debt. Even with tests, the more complex the code base is, the more risky it is to vibe-code on it without introducing more bugs [0] and increasing the debt. Does not matter if the CI is green or if all the tests pass. It gets even worse if you can't explain the change / pull request or what the implications are after applyin…

Post by lifthrasiir » Mon, Jun 22, 2026, 8:49 AM UTC

applfanboysbgon wrote: post #21

indiv0 wrote: post #14

This thread will become a typical "haha slop company made slop" but I've been bitten by a bug exactly like this before in a (pre-AI, artisan) OSS project. The maintainer there didn't properly account for DST when calculating last backup time, so the app started and never stopped writing/re-writing backups continuously. Perhaps the framing shouldn't be "haha slop" but rather why doesn't the AI write better quality sof…

1. I bet that developer only made that mistake one time in their life. Humans learn from their mistakes, LLMs don't. If you rely on LLMs to generate all of your code, you can expect to run into the same issues again and again. 2. "One developer somewhere in the world made a bad mistake one time, so this represents the quality of all software devs everywhere". Maybe they were just a bad developer? Bad developers exist…

Post by applfanboysbgon » Mon, Jun 22, 2026, 9:03 AM UTC

lifthrasiir wrote: post #27

applfanboysbgon wrote: post #21

Earlier quoted context omitted.

1. I bet that developer only made that mistake one time in their life. Humans learn from their mistakes, LLMs don't. If you rely on LLMs to generate all of your code, you can expect to run into the same issues again and again. 2. "One developer somewhere in the world made a bad mistake one time, so this represents the quality of all software devs everywhere". Maybe they were just a bad developer? Bad developers exist…

> I have never written a bug that has destroyed my users' hardware, ... Probably whoever (human or agent) originally decided to put TRACE logs into SQLite also thought---or reasoned---so. Maybe the decision was right at that time but the amount of TRACE logs have increased enormously. You will never know.