Error 429 happens more often than in the WebUI about vscode-chatgpt

[gregid]

In order to reproduce it you need to get timed out error first. Then when you try after timeout you will get 429 that keeps with every following request.

[gregid]

I believe timeout error is crucial for reproducing - also each time the error happened was from the conversation window.

[gregid]

OK, something interesting is happening - clicking the new button Clear conversation also fixes the problem (without reloading window). This may indicate that the problem lies somewhere else than 429.

[gencay]

429 is basically a Too many requests error. Meaning that you need to give it a few moments to retry. Clear conversation re-instantiates the chatgpt api. OpenAI APIs rate-limit requests coming from outside of their web apps. The reason why it started working for you after a clear conversation, could be that you gave a few moments to retry submitting your request.

[gregid]

I don't think so - I've had this situation at least 10 times - no matter how much time I gave it didn't help, clearing session also didn't help only reloading window or now clearing conversation helps.
I cleared conversation 1 second after I tried to send query (and got the error again).

[gencay]

Alright, let me try to reproduce the issue on my end. Thanks a lot for reporting it!

[gencay]

My repro scenario:

• I keep hitting Add Tests until I see a 429
• Once in 429 error state, all my next queries run into 429
• I wait for a few seconds (Until I see a response for the very first question I asked initially)
• After I receive a response, I am able to send new prompts without errors
• During this I don't restart vscode nor do I clear conversation.

I cannot repro your problem but I need to wait until I get a response for my initial request that I didn't receive a 429 for.

[gencay]

Ok. I will try to repro again.

There were a few error handling updates on the API wrapper package I'm using. I did update it to latest in case that'd help. It's on v1.6.2 and is being rolled-out to marketplace now.

[gregid]

OK, got 1.6.2 already - will be hunting for elusive timeout :)

[gencay]

Seems like other people are also seeing this: transitive-bullshit/agentic#111 . Closing this since it's on OpenAI to block requests after a timeout. Clearing conversation / Resetting thread will help unblock the flow.

[gencay]

Resurrecting this thread since with v2, the extension will now work flawless using the browser behind the scenes for the ChatGPT prompts. FYI @gregid please update your extension to latest and let it log you in, keep the browser open and ask ChatGPT your questions as usual.