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
[–] [S] 1 point 11 months ago (2 children)

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.

  • source
  • parent
  • hideshow 2 child comments
  • [–] 1 point 11 months ago* (last edited 11 months ago) (1 child)

    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.

  • source
  • parent
  • hideshow 1 child comment
  • [–] [S] 1 point 11 months 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".

  • source
  • parent