You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
[bug] Connection Timeout Error Leading to Service Crash When Using ai generate code Feature #217
I think we saw something similar when a user did not have access to the model. Is it possible your API key does not permit access to chatgpt-4o-latest? cc @nichochar who I think saw this before.
No, I have not seen timeouts like this before. What we saw in the past was a "This model is not available for your account" error.
This looks suspiciously like an issue on the openAI side, especially given what I see on https://status.openai.com:
@swk777 can you try again, and maybe also try a different model (you can switch to gpt-4o for example in the settings), and confirm that this is still an issue?
I suppose the issue isn’t related to the OpenAI side. The timeout occurs when accessing openai.com, and the exception is thrown from generateText due to this, as there’s no protection against it in the code snippet shown.
Activity
benjreinhart commentedon Aug 27, 2024
I think we saw something similar when a user did not have access to the model. Is it possible your API key does not permit access to
chatgpt-4o-latest? cc @nichochar who I think saw this before.nichochar commentedon Aug 27, 2024
No, I have not seen timeouts like this before. What we saw in the past was a "This model is not available for your account" error.
This looks suspiciously like an issue on the openAI side, especially given what I see on https://status.openai.com:
@swk777 can you try again, and maybe also try a different model (you can switch to
gpt-4ofor example in the settings), and confirm that this is still an issue?swk777 commentedon Aug 30, 2024
I suppose the issue isn’t related to the OpenAI side. The timeout occurs when accessing openai.com, and the exception is thrown from generateText due to this, as there’s no protection against it in the code snippet shown.
