Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

Codex logging bug may write TBs to local SSDs

github.com

Post reply on HN
Print view View original

31–40 of 296 posts

Re: Codex logging bug may write TBs to local SSDs

#31

Post by cncjvu7 »

l33tman wrote: post #26
b--l wrote: post #10

Codex is one of the most infamous examples of slopware. Just having the window unhidden on my mac will cause it to use 100% of the GPU displaying the spinner message. THE SPINNER MESSAGE CAUSES 100% GPU USAGE ON AN MBP M5!! So any time you're waiting on the model (which is 90% of the time), your fans will be blasting (careful, don't use it on battery). The issue is on github and close to 6 months old. Probably since…

This was fixed long ago, if I'm thinking of the same bug. It was stuck in an inf loop all the time the codex window was open.

Nah it's still doing weird shit. Uninstalled that crapware last week.

Re: Codex logging bug may write TBs to local SSDs

#32

Post by SilverSlash »

sleples wrote: post #22
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…

We've gone from "you're holding it wrong" to "the training data was bad because humans suck too". Difference is, humans learn from their mistakes.

> Difference is, humans learn from their mistakes.

Great! So next time the human will prompt the agent to watch out for and avoid this bug.

Re: Codex logging bug may write TBs to local SSDs

#33

Post by [deleted] »

HPsquared wrote: post #25
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…

There are going to be sooooo many consulting opportunities after this wave.

[deleted]

Re: Codex logging bug may write TBs to local SSDs

#34

Post by matharmin »

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…

LLMs do learn from mistakes. Not as directly from individual mistakes like humans do, but in aggregate the models have improved much more in the last year than most humans I know learn in the same time.

Re: Codex logging bug may write TBs to local SSDs

#35

Post by lifthrasiir »

applfanboysbgon wrote: post #29
lifthrasiir wrote: post #27

Earlier quoted context omitted.

> 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.

I love that we've moved the goalposts from "LLMs are better than artisanal software engineers" to "actually, shipping hardware-destroying bugs in production is literally unavoidable, nobody could possibly avoid doing it".

I only meant what I said. After all the OP's thesis was that LLMs aren't better than artisanal software engineers, are they? There was no goalpost to move at least in this particular thread. And the solution might be another agent monitoring those oft-ignored signals.

Re: Codex logging bug may write TBs to local SSDs

#38

Post by cedws »

consp wrote: post #3

Why didn't the review process spot this obvious error? Oh wait ... @codex review this

Moreover why isn't the bug fixed already? I thought programmers were obsolete now. Surely one of the leading AI labs has figured out full automation of software development end-to-end by now if that's so.

Re: Codex logging bug may write TBs to local SSDs

#39

Post by i2km »

Shocking. Been open a week and AFAICT just silence from OpenAI. I just find it baffling. You'd think that these vendors would be very sensitive to this sort of issue. I mean, surely they have multiple agents hooked up to github monitoring potential issues and proposing fixes, right? ...right?

Surely it should be trivial for them to have their own tools spinning away trying to fix all the github issues in real time...

Re: Codex logging bug may write TBs to local SSDs

#40

Post by ponector »

SilverSlash wrote: post #32
sleples wrote: post #22

Earlier quoted context omitted.

We've gone from "you're holding it wrong" to "the training data was bad because humans suck too". Difference is, humans learn from their mistakes.

> Difference is, humans learn from their mistakes. Great! So next time the human will prompt the agent to watch out for and avoid this bug.

You are a senior developer. Please do no mistakes!
Post reply on HN