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

41–50 of 296 posts

Re: Codex logging bug may write TBs to local SSDs

#41

Post by jofzar »

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…

> Codex is one of the most infamous examples of slopware

Woah, let's not forget Claude code is right there

Re: Codex logging bug may write TBs to local SSDs

#42

Post by jofzar »

59nadir wrote: post #18
ares623 wrote: post #13

i hope they find the smoking gun, the key insight, the kicker.

Then they can apply a clean solve , the cleanest solution . It's fascinating how offensive some of this verbiage becomes to you when you see it attached to LLM output too much.

Ugh this one's gets me so bad, same with "wire" and "wired" everything is wired to something.

Re: Codex logging bug may write TBs to local SSDs

#43

Post by xpct »

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…

Well thank you for your service. I thought about trying out Codex after the disaster that is Claude Code. I'll be fine without either one on my machine

Re: Codex logging bug may write TBs to local SSDs

#44

Post by fn-mote »

da_grift_shift wrote: post #30
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…

What are your thoughts on the SNR of the linked GitHub issue threads? Consider the volume of comments posted and the substance of each comment.

I read the first page and they were excellent. Each was clearly written by an experienced dev who knows how to substantiate their claims and propose an acceptable fix that could just be merged.

Your comment, on the other hand, would be improved by including your own opinion on the matter.

Re: Codex logging bug may write TBs to local SSDs

#45

Post by Imustaskforhelp »

cryo32 wrote: post #36
neuralkoi wrote: post #28

Vibe coding takes "move fast and break things" to a whole nother level.

Yeah. Here I am sitting on a major incident at our company because someone’s vibe coded shit went seriously wrong.

Can you talk more in detail if possible and are allowed to do so?

I do know one instance of someone literally losing a job because they vibe-coded their way to prod. Their response/justification was: "The code wasn't written by me. It was written by Claude/Chatgpt"

They hadn't done anything to the database itself but you betcha that there are some horror stories involving database, lack of proper backups and Vibe-coding gone insanely wrong.

Re: Codex logging bug may write TBs to local SSDs

#46

Post by xpct »

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…

Lack of accountability is the cause here. People don't think before hitting the 'Publish' button. Their managers let them off the hook because the culture still allows making egregious mistakes, as long as there's an LLM to blame.

Re: Codex logging bug may write TBs to local SSDs

#48

Post by xpct »

matharmin wrote: post #34
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…

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.

I don't like the reframing of 'learning from mistakes' from a human-like, near instantaneous feedback loop, to a year-long process of retraining on many traces collected from user data. They're different concepts and we should refer to them using different phrasing.

Re: Codex logging bug may write TBs to local SSDs

#49

Post by [deleted] »

fn-mote wrote: post #44
da_grift_shift wrote: post #30

Earlier quoted context omitted.

What are your thoughts on the SNR of the linked GitHub issue threads? Consider the volume of comments posted and the substance of each comment.

I read the first page and they were excellent. Each was clearly written by an experienced dev who knows how to substantiate their claims and propose an acceptable fix that could just be merged. Your comment, on the other hand, would be improved by including your own opinion on the matter.

[deleted]

Re: Codex logging bug may write TBs to local SSDs

#50

Post by mvATM99 »

jofzar wrote: post #41
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…

> Codex is one of the most infamous examples of slopware Woah, let's not forget Claude code is right there

Yeah exactly.

I'm not exactly building TUI's every day, but even i felt pain when i read that "small game engine" post

Post reply on HN