back
1 comments
I actually don't believe ChatGPT made this mistake. Maybe one of their engs made it and then decided to blame ChatGPT. I can't get ChatGPT to reproduce this error. I wonder what their prompt was.

I use ChatGPT constantly and it is not the type of error it would make. It is such a common pattern.

And if you ask GPT-4o whether the code is correct, it is able to spot the issue.

> I can't get ChatGPT to reproduce this error. I wonder what their prompt was.

They were having it translate NextJS code to Python, so the prompt probably included their NextJS code (actually, since they’d never turned on the feature that led to them realizing the problem in NextJS, and maybe didn't have enough volume to hit it on the other pathways that the Python code had it on, it’s not implausible the same bug existed in their NextJS code but was never triggered, and ChatGPT just translated the bug. But in any case, their prompt would include their proprietary code to translate.)