Live data from Hacker News

Codex logging bug may write TBs to local SSDs

github.com

281–290 of 296 posts

Re: Codex logging bug may write TBs to local SSDs

#281
post #193

Earlier quoted context omitted.

Claude Code supports native imports: `@AGENTS.md`

You two realise that symlinks exist, right? That you need neither a "plugin" nor a "native import"?

What if I need Claude-specific instructions?

Re: Codex logging bug may write TBs to local SSDs

#284

Earlier quoted context omitted.

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-cod…

> 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" People like that and their managers should all be put on PIP right away. It's not like there is a lack of talent on the market.

Say in an interview that you are sceptical of ai and you won't get the job.

Re: Codex logging bug may write TBs to local SSDs

#285
post #282

Hey everyone, I'm an engineer at OpenAI. Thanks for the discussion here. Just wanted to report that a fix for this issue has been published in an update to the CLI and Codex App.

Looks like the fix doesn't work for all users from the comments on Github, please verify.

Re: Codex logging bug may write TBs to local SSDs

#286

Earlier quoted context omitted.

I believe this is because they don’t lazyload the document. The entire conversation sits in the DOM.

Yeah - is such a large dom of essentially text expected to be that slow? For what it's worth I use a small script that essentially deletes old chat messages DOM nodes which significantly speeds it up.

Yes, because under the hood it’s much more than just text. It’s not hard to imagine dozens if not hundreds of elements are contained within each prompt+reply pair.

I bet there’s also some React performance issues involved here too

There are some real table stakes FE perf issues with the ChatGPT site

Re: Codex logging bug may write TBs to local SSDs

#287

Earlier quoted context omitted.

Someone choosing different tradeoffs is not them making an error.

It's obviously an error, but I'm going to assume you are larping and move on

What is the error? I explained how it is not an error and your are giving vague responses.

Re: Codex logging bug may write TBs to local SSDs

#288
post #265

Earlier quoted context omitted.

Claude Code has been out for just 1 year and has millions of users already, being a major contribution to roughly $40 billion in revenue. By any stretch it is one of the most extremely fast developed products driving the most important workflow for millions of people already. "Why isn't literally everything about a product that came out a year ago with an extremely fast scaling userbase solved?" is what I hear. The g…

Or until you people finally admit the king was naked

Yes all the F500 companies have been paying eye watering $$$ for Claude Code for half the year because “the king was naked” Those ruthless cost savings corporations, they surely never care about trimming extra spend

Re: Codex logging bug may write TBs to local SSDs

#289
post #265

Earlier quoted context omitted.

Or until you people finally admit the king was naked

Yes all the F500 companies have been paying eye watering $$$ for Claude Code for half the year because “the king was naked” Those ruthless cost savings corporations, they surely never care about trimming extra spend

They've been paying people to teach NLP for several decades when it's well known it's all made up.

Why would they act rationally on this one single specific thing?

Post reply on HN