Live data from Hacker News

Codex logging bug may write TBs to local SSDs

github.com

231–240 of 296 posts

Re: Codex logging bug may write TBs to local SSDs

#231
post #219
post #192

Earlier quoted context omitted.

I beg people to learn what symlinks are. The fact that "put @AGENTS.md in there" is a "common workaround" shows why programmers (good ones at least) are not going anywhere soon.

Good programmers know symlinks are not portable

Neither are line endings. But like line endings, I just put it into git and get over it.

Re: Codex logging bug may write TBs to local SSDs

#232

Earlier quoted context omitted.

> same "profit reducing red tape" that civil engineers or similar face. I don't think we should ever head toward licensing/a credential body for software development, but I do think now is a good time to have discussions around liability for defective products. A good start would be to stop allowing companies to disclaim all warranties of fitness for a particular purpose in their EULAs. The joke of Microsoft Copilot…

> I don't think we should ever head toward licensing/a credential body for software development, but I do think now is a good time to have discussions around liability for defective products. Liability is how a credential body would organically grow. It already exists in the security, compliance, and enterprise parts of the software world.

That can be okay. The problems we're worried about come when it's government mandated.

The EU Cyber Resilience Act puts heavy liability on vendors for software vulnerabilities that get exploited, including in open-source components they incorporate. OSS devs are shielded - liability is on the companies who incorporate OSS into commercial stuff.

Re: Codex logging bug may write TBs to local SSDs

#233
post #171

Earlier quoted context omitted.

> yet that's a human thing. is this joke? Here we are talking about trillon dollar AI companies who claim AI can fix decade old bugs and create new compilers, OSs and what not. Are parallel agents working autonomously to fix issues as well as create new features not allowed at these companies?

Humans still decide what LLMs do in a code base, full stop.

Why not just tell it to do everything on the task list and then tell it to fix all bugs?

Re: Codex logging bug may write TBs to local SSDs

#234
post #171

Earlier quoted context omitted.

> yet that's a human thing. is this joke? Here we are talking about trillon dollar AI companies who claim AI can fix decade old bugs and create new compilers, OSs and what not. Are parallel agents working autonomously to fix issues as well as create new features not allowed at these companies?

Humans still decide what LLMs do in a code base, full stop.

Yea it's too bad these poor scrappy startups cannot afford engineers to build decent software.

Re: Codex logging bug may write TBs to local SSDs

#235
post #203

Earlier quoted context omitted.

Two trends I see at work: 1) No more human written code in projects, all code must be AI generated. 2) Developers are responsible for all code AI generated. Combine that with fear of losing job and you have no one calling out management bullshit on their face.

I don't see how these things conflict. Nor did I get the point you were making in the sarcastic upstream comment. It is obviously the case that you can both delegate code implementation to AI and also be responsible for it. You are signing off on the code you submit to a project no matter where you got it from nor how it was generated nor who you delegated the task to ("actually my friend wrote it so if it sucks don'…

They don't conflict, if the generated code is acceptable. Maybe I'm holding it wrong, or I'm not using the right combination of plugins and MCPs. But if I'm not allowed to manually correct the generated output, then I am forced into a loop of generating corrections until it's good enough to stake my job on. I hope you can see that such a policy would be ridiculous.

Re: Codex logging bug may write TBs to local SSDs

#236
post #64
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…

if we are at 10x with AI and near AGI or ASI, then how is it possible that these products (Codex, Claude Code CLI) are still such garbage? shouldn't this "agentic AI revolution" have long solved this already? no way they're over there saying "we are on it plz wait" or that "it's too much effort"?

Gemini is also buggy as heck and has been buggy for years. For a company of Google's size with "all the power of AI" it's seriously embarrassing.

Re: Codex logging bug may write TBs to local SSDs

#237

Earlier quoted context omitted.

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

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)

Re: Codex logging bug may write TBs to local SSDs

#238

Earlier quoted context omitted.

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

I created a Claude Code plugin to load AGENTS.md. Uses symlinks but it’s better than no support. https://github.com/hexsprite/claude-agents-md

What’s actually better is doing a symlink by hand. 1- if you didn’t know it you learn what’s a symlink; 2- if that’s in a git repo you share it with all your coworkers without all of them needing to install the plugin; 3- security-wise it’s way better than running some 100+ lines of Bash from a repo on GitHub.
Post reply on HN