-
Notifications
You must be signed in to change notification settings - Fork 113
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
fix: error handling if user has no access to gpt4 yet #26
Comments
good first issue imo |
fosho— def has confused some ppl |
I can take this. I was also thinking about the options that are there. I would say that we need to check it every time not only when used firstly pastes API key or later changed it because if initially his API didn't have access to GPT-4 but later on they were granted access, we may not be aware of that. I think it will be also nice to only disable it in the list of option and provide link where to join the waitlist. |
nice, this all sounds right to me, though i lean towards reducing complexity wherever possible — so maybe we dont block off GPT-4 in the dropdown but just check when they select it, and show a toast or something saying "you don't have access to this model, click here to sign up for the waitlist" etc? |
Sounds great! I will also add check that if someone without access to GPT-4 but with GPT-4 selected will automatically roll on GPT-3.5-turbo. |
Just want to let I will have time to work on this on weekend, if someone wants he can pick it up |
@AdamSchinzel happy to take this one over if you haven't started working on it yet! |
The problem
At the moment, GPT4 rollout isn't available for everyone yet, if an API key is used that does not have access yet we should at least show something.
Error when calling model
Multiple ways to fix:
2 and 3 can maybe be done in combination because if a user gets access while they already had supplied the key on Flux they would have to switch api keys for it to refetch this information.
The text was updated successfully, but these errors were encountered: