138

During OpenAI’s GPT-5 launch event, they demoed the model’s ability to fix real bugs in production code. Live on stage. In their own repository. The kind of demo that makes CTOs reach for their credit cards and engineers nervously update their resumes. There’s just one small problem: the fix they promised to merge “right after the show” is still sitting there, unmerged, three and a half months later.

you are viewing a single comment's thread
view the rest of the comments
[-] Kissaki@programming.dev 34 points 3 weeks ago

The issue, presumably the PR (linked at the top of the issue because of reference).

Look at the code change. It gets inputs and loops over them and seems to do an in-place fixup. But the code indent is wrong, and it even changed the function definition of the unrelated next function. In Python, the indent-logic-significance language.

I assume they briefly showed the code on stage. Even then it should have been obvious to any developer. py file, messy indent, changes unrelated function.

Please correct me if this is the wrong PR.

[-] Yoddel_Hickory@piefed.ca 14 points 3 weeks ago* (last edited 2 weeks ago)

Actually the function definition is unchanged. The line that was "added" at the bottom was also "removed" at the top. This is just the Git diff generator being confused, which won't come as a surprise to anyone that has ever used it.

The indendentation really is messed-up though.

[-] Kissaki@programming.dev 1 points 2 weeks ago

An indentation change is a definition code change. And as I pointed out, it's a py file, and Python is an indent-significant language.

[-] Yoddel_Hickory@piefed.ca 1 points 2 weeks ago* (last edited 2 weeks ago)

Of course, but you said:

But the code indent is wrong, and it even changed the function definition of the unrelated next function.

It is weird to split the two in your sentence, as only the indentation of the next function definition was changed, not the definition itself.

You can just take the L and say you didn't see that the function definition that was "added" was just "removed" at the top. It is an easy mistake to make, I know I've done it many times.

[-] Kissaki@programming.dev 1 points 2 weeks ago

You can just take the L and say you didn’t see that the function definition that was “added” was just “removed” at the top.

That's not what happened though.

Changing the indent of the def changes the definition. That's my whole argument.

I don't get why you say "of course", agreeing with my point, but then "it was only the indentation that was changed".

load more comments (7 replies)
this post was submitted on 22 Nov 2025
138 points (100.0% liked)

Programming

23868 readers
412 users here now

Welcome to the main community in programming.dev! Feel free to post anything relating to programming here!

Cross posting is strongly encouraged in the instance. If you feel your post or another person's post makes sense in another community cross post into it.

Hope you enjoy the instance!

Rules

Rules

  • Follow the programming.dev instance rules
  • Keep content related to programming in some way
  • If you're posting long videos try to add in some form of tldr for those who don't want to watch videos

Wormhole

Follow the wormhole through a path of communities !webdev@programming.dev



founded 2 years ago
MODERATORS