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

1–10 of 296 posts

Re: Codex logging bug may write TBs to local SSDs

#5

Post by Imustaskforhelp »

I don't understand how Codex can blunder so badly. I imagine that even if they would be using vibe-coding, surely they must have some good engineers. So why is there such severe bugs?

One can argue that these products are the flagship products of their respective AI companies aside from the AI models themselves of course.

I imagine that this story will be picked up by the news left and right, some stories just feel this way and this one is like that (given 12 upvotes on HN in 7 minutes)

The only logical conclusion (from this incident) that I can have is: An (vibe-coded?) product is hard to maintain even for some of the best engineers and is bound to have severe bugs.

2. Proper testing and taking issues seriously is the key if you still wish to do this and there isn't much. This is a week old issue which I can only classify as severe.

I wish to keep an nuanced opinion about it but oh this is bad for openAI (not as bad as them accepting autonomous AI within drones and mass surveillance though)

My point is: AI has both uphills and downward valleys and cliffs. It might as well just accelerate you, which could be, towards your downfall as well. Its recommended to keep an eye while driving and not drive too fast.

AI companies might be like car companies which don't offer a brake pedal.

Re: Codex logging bug may write TBs to local SSDs

#7

Post by b--l »

ramon156 wrote: post #6

Blegh, I puke every time I see obviously AI generated comments in GH PR's. You cannot assume any of these people have done their research, other than telling Codex to do it for them

It's because they use gpt-5.5-xhigh (the money making* model) to build it.

(*for them)

Re: Codex logging bug may write TBs to local SSDs

#9

Post by charcircuit »

consp wrote: post #3

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

Because it's not an error. The software is working as the creators intended. The diagnostic data (trace logs) are intentionally being saved for debug purposes.

Re: Codex logging bug may write TBs to local SSDs

#10

Post by b--l »

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 the release of vibe coded junk. I would literally fix it myself but it's closed source for whatever reason.

There are many discussions about which model is better, or if vibe coding is even possible. I point you to the extent of what one of the most well funded, money flush, well staffed model making companies can do with vibe coding.

To me a screwup this bad (where the CEO has already made it clear they're now "focussing on coding") indicates that there's something truly broken in the company. No one on polymarket expects them to have a leading model any time soon for example.

It's a tragedy. The world needs competition to anthropic.

Post reply on HN