Skip to content
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

gpt-3.5-turbo-0613 is being deprecated on 6/13/2024; need to update to gpt-3.5-turbo-instruct #32

Open
princetrunks opened this issue Jun 2, 2024 · 2 comments

Comments

@princetrunks
Copy link

I saw that if using the OpenAI apis that the model used in the chat function, gpt-3.5-turbo-0613 , will be soon deprecated and might not work.

As per this page:
https://platform.openai.com/docs/models/gpt-3-5-turbo

I confirmed on my instance that changing line 122 in supabase/functions/chat/index.ts to gpt-3.5-turbo-instruct works with uploaded documents/ previously saved embeddings. Going to any other will not work and the chat will not know of the documents as it seems that the structure of completionStream or completionMessages might need to be refactored for newer models. This from how OpenAI states that the gpt-3.5-turbo-instruct model still uses legacy completions.

@gregnr
Copy link
Collaborator

gregnr commented Jun 5, 2024

Good catch @princetrunks about the model deprecation - we should update this. I'm a bit surprised that gpt-3.5-turbo-instruct worked for you though since that uses the legacy completions endpoint vs. chat-based endpoints (which we use in this repo). Did you have to modify any other code as well?

In other projects I've simply updated the model to the latest version. Any reason gpt-3.5-turbo-0125 shouldn't work here from your perspective?

@princetrunks
Copy link
Author

Hey @gregnr. No problem. Yeah, I was shocked it worked as I tried gpt-3.5-turbo-0125 prior and that oddly didn't work. My completion object is the same. I didn't log / save what the error was before I got instruct to work but I'll see if I can see what that might be. My completion object is the same as the one in the repo. I duplicated the functions and frontend so I'll do a comparison in my next push to my dev site.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants