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

Errors with new GPT-4 and GPT-3.5 versions #220

Closed
atzitzeras opened this issue Sep 20, 2023 · 1 comment · Fixed by #336
Closed

Errors with new GPT-4 and GPT-3.5 versions #220

atzitzeras opened this issue Sep 20, 2023 · 1 comment · Fixed by #336
Labels
bug Something isn't working
Milestone

Comments

@atzitzeras
Copy link

When attempting to use GPT4 0613 or GPT3.5

The following error comes up:
The completion operation does not work with the specified model, gpt-4. Please choose different model and try again. You can learn more about which models can be used with each operation here: https://go.microsoft.com/fwlink/?linkid=2197993.

This looks like a code base error as the Completion operation is not supported by gpt-35-turbo(0613) and gpt-35-turbo-16k(0613) models. These models only support Chat Completions API. Only older turn model - GPT-3.5 Turbo (0301) supports both Chat and completions API. Please refer to the GPT-3.5 models for details.

On top of that, the accelerator is also using the old version of even GPT3.5, 0301. we need to switch to the new version, 0613, which yields better results. This will require the step above as well.

This should be configurable and not hard coded on the bicep.

Reference to the Bicep code https://github.com/microsoft/PubSec-Info-Assistant/blob/deb64086a5b1c5b720fdd6e7dbded05db7f8d2cc/infra/main.bicep#L180C9-L187C46

model: {
format: 'OpenAI'
name: chatGptModelName
version: '0301'
}
sku: {
name: 'Standard'
capacity: chatGptDeploymentCapacity

@dayland
Copy link
Contributor

dayland commented Sep 25, 2023

A temp HF was put in to move to the recommended model and version in #226 .

An additional fix is coming to honor the user configured values even in the default BICEP deployment.

@dayland dayland added the bug Something isn't working label Nov 2, 2023
@dayland dayland added this to the 0.4-Delta milestone Nov 2, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants