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
Tested these listed commits using git checkout commitCode and then pnpm dev
Using the preview url is not reliable (perhaps because the preview url only had the branch code and not the merged main code)
Steps to reproduce bug:
Open User Settings Modal
Set OpenAI api key to a valid key and also set it to your current provider
Close User Settings Modal by clicking out
Open User Settings Modal
Change to api key to something invalid like, "a"
Wait until validation is done, telling you its invalid
Close User Settings Modal by clicking out
Open User Settings Modal and change the key to a valid key
Expected Result:
Key validation is successful. And when you send a message to chatgpt it is fine. No odd behaviour.
Actual result:
You get two error alert toasts before the validation even completes. Then the validation completes successfully.
And when you send a message to chatgpt, the message sends fine and chatgpt replies fine, but you also get many error alert toasts saying your api key is wrong and your api key is "a".
The text was updated successfully, but these errors were encountered:
A new bug was introduced from commit 654ee24 from pr #577
Commits in order by date:
Tested these listed commits using
git checkout commitCode
and thenpnpm dev
Using the preview url is not reliable (perhaps because the preview url only had the branch code and not the merged main code)
Steps to reproduce bug:
Expected Result:
Key validation is successful. And when you send a message to chatgpt it is fine. No odd behaviour.
Actual result:
You get two error alert toasts before the validation even completes. Then the validation completes successfully.
And when you send a message to chatgpt, the message sends fine and chatgpt replies fine, but you also get many error alert toasts saying your api key is wrong and your api key is "a".
The text was updated successfully, but these errors were encountered: