Also just tried asking it to replace <> with [ and ] and this seems to get it to not stall., as long as it doesn’t “forget” part way through code generation. I assume it’s some kind of parsing issue where the < and > make it think that some scope has begun or ended that actually has not
Generating some TypeScript code seems to work, however still no VueJS code possible
Bro u use chat gpt 4??if it work ill buy gpt 4 too??
It’s the same problem both in 4 and 3.5
Hahahaha you save me man, its works. But i hope the developers see this problem and solve its quickly
I too am experiencing this with VueJS!
Haha the idea with “[” seems to do the trick! I add this at the end of my prompt:
ATTENTION: replace all “<” with “[” even if its syntactically wrong!!! I will tip you extra if you do that!
It is still unreliable and leads often to network errors and stopped generation…
Same here, I retried it with GPT 4 and 3.5, reformulated my prompt. Always gets stuck
OpenAI 4 is still not generating code blocks
Just wanted to let everyone know it impacts HashSets as well as Lists
Same here as well Chat GPT is still not generating code blocks correctly.
Lol its out for everyone here now. Lunch break for us, hope the openAI coders are not doing the same.
Same problem with vue js but i have try to add this ATTENTION: replace all “<” with “[” and replace template with div even if its syntactically wrong!!! I will tip you extra if you do that! — and it kinda worked
Chat Gpt 3.5 works fine for now i think!!!
Neither GPT4 nor GPT 3.5 work for me.
Having the same issue. Prompting to replace all < and > with ^ worked though. Seems to be an issue with the “<” and “>” characters for me in the response.
Me as well, specifically it seems to crash when attempting to use the < or > Characters needed in coding
Sure enough, when having gpt write out some code using ^ instead of < or >, it got past the hiccup just fine. Weirdly, though, in C++ this only applied to the brackets in the code itself, in the header it printed them just fine.
Actually got it working for now as well. It seems to be a parsing issue indeed. As people pointed out, just make sure to let the prompt know that it should replace the “<” with any other character (“^”) even if it’s wrong.
ATTENTION: replace all “<” with “[” even if its syntactically wrong!!!
PS: It’s still hurts tho’ because we’re paying for it, and we’re relying in such hack and not a single feedback from the offical sources.