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

271–280 of 296 posts

Re: Codex logging bug may write TBs to local SSDs

#271

Post by tomjakubowski »

theowaway213456 wrote: post #132
altcognito wrote: post #123

I think part of the question should be, why is there no QA or test that catches this? It's one thing to be slopware, but why didn't anything run a test that catches this?

Every time you write a test that handles some data, you write an assertion about how much data is handled? Come on, this is such an easy thing to forget to test. Don't act like there is some magical testing strategy that would have caught this

The most likely way I think you'd catch this in a test would be by accident, running some kind of long-running integration test for other purposes, and then finding the disk gets filled up in CI (or on a developer machine).

Re: Codex logging bug may write TBs to local SSDs

#272

Post by sleples »

klibertp wrote: post #145
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.

A singular human does (or tends to). Humans as a group, where members join and leave a group with time, also do learn, but at a much slower pace - over the years to decades timeframe. "X things programmers should know about Y" is a template for quite a few very influential blog posts, yet for most of them, you find many programmers, even decades later, who don't actually know what they "should". My experience was alw…

OpenAI developers presumably get paid far more than average, so I'd expect better from them, and maybe I'm overrating the average developer, but I can't see a team of average developers struggling with the multitude of ridiculous bugs like OpenAI/Anthropic have for software that amounts to a CLI wrapper making API calls.

Re: Codex logging bug may write TBs to local SSDs

#273

Post by DrewADesign »

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…

> it's closed source for whatever reason.

When working in an organization that defaulted to open sourcing everything, (even side projects,) there was only one reason any of us would keep something closed — embarrassment. Nobody wants to be the public face of some garbage code base. I’m sure that’s triply true when you’re using that code to justify exorbitant pricing.

Re: Codex logging bug may write TBs to local SSDs

#274

Post by thejazzman »

lelandbatey wrote: post #269
fortuitous-frog wrote: post #208

Earlier quoted context omitted.

I used to use a symlink but was concerned that Claude might see the presence of an "AGENTS.md" file (in e.g, a "List Files" tool call output or from a direct `ls`), be curious and attempt to read it directly (not knowing that it's the same as the "CLAUDE.md" file auto-injected by the harness), and essentially double the token impact / context bloat. Indeed, I did some local experimentation and noticed this was the ca…

Your solution "appears" to solve the problem, but without any information about how exactly that solution works, it's just magic an vibes. Does the harness parse the contents of CLAUDE.md, see the @AGENTS.md and then inject the contents of AGENTS.md into that file with a note saying "hey Claude-the-llm, here's the contents of AGENTS.md per an @reference"? Does the harness parse and inject but WITHOUT any ceremony tel…

why over complicate it? the answer is obviously yes? it sees it and reads the file? might it sometimes not? yeah, just like every other thing you write in agents.md or the prompt. if you want to write a more verbose statement telling it to read the other file do so. or if you really want to make damn sure it read what you wrote, then symlink it, because it does in fact read the thing twice.

Re: Codex logging bug may write TBs to local SSDs

#276

Post by supah »

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…

Back in the early days, people were saying the world needs Anthropic as a competitor to ChatGPT. Full circle.

Re: Codex logging bug may write TBs to local SSDs

#277

Post by dgunay »

me551ah wrote: post #122
jofzar wrote: post #41

Earlier quoted context omitted.

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

Claude is also weird for being the only coding assistant that for some reason doesn't support AGENTS.md. Codex, Amp, Cursor all of them support it and read from it, but not claude which forces it's users to use CLAUDE.md instead. The issue is the higest voted issue on their gitlab repo: https://github.com/anthropics/claude-code/issues/6235

Maybe I'm just not aware enough to notice any quality degradation, but I've been using Claude Code in repos that only have AGENTS.md and it just generally seems to know to read it when getting its bearings.

Re: Codex logging bug may write TBs to local SSDs

#279

Post by bandrami »

hk__2 wrote: post #237
bandrami wrote: post #178

Earlier quoted context omitted.

So there's this amazing thing called a symlink

Not amazing enough. Let me present you claude-md-symlinker [1], an 8k-lines Rust project designed to do exactly the same as a symlink but in an obscure manner, running as a Linux service and maintaining its own database. This is like left_pad but for symlinks. [1]: https://github.com/dutifuldev/claude-md-symlinker#claude-md-... (I’m not the author obviously)

A few years ago I noticed a junior dev was creating a lot of one-file, two-branch git repositories and I asked him why. He said he wanted to run a diff on two versions of a file that wasn't in version control, so he would make a branch with each version and run git diff.

I think about that a lot lately.

Re: Codex logging bug may write TBs to local SSDs

#280

Post by charcircuit »

anematode wrote: post #246
charcircuit wrote: post #9

Earlier quoted context omitted.

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.

What?

Someone choosing different tradeoffs is not them making an error.
Post reply on HN