-
Notifications
You must be signed in to change notification settings - Fork 430
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
Azure OpenAI issue #64
Comments
I have fixed the extra parenthesis in the generated URL, sorry about that. Beyond that, I don't have any insight into what those values should be or how to test it. Microsoft denied my application to access the Azure OpenAI endpoint, so I'm just guessing based on documentation. Can you give me an example of a correct HTTP request that works for you, including all headers except authorization? That way to can try to make sure this SDK works similarly. |
I have access to Azure OpenAI. I will look into this today and provide feedback. I hope I can be of help. |
Sorry, I missed the answer to the issue. I'll try to test it today too. |
Just wanted to add to this thread that - it's all working fine for me, with an Azure OpenAI deployment. The parenthesis fix was all that was needed. |
I confirm that the parenthesis issue is fixed and it's working fine now 👍 |
This's the console of Azure OpenAI. The blue part is 'YourResourceName' and the red part is 'deploymentId'. Hope this helps you. And don't worry. Your SDK is perfectly usable. |
This works for me. HttpRequestMessage request = new()
{ |
I have tried with gpt-35-turbo (version 0301) and 2023-03-15-preview and it's ok. |
I'm trying to use this library with an Azure OpenIA resource.
I'm using the example in the readme:
OpenAIAPI api = OpenAIAPI.ForAzure("YourResourceName", "deploymentId", "api-key");
, but Url created seems to be wrong.OpenAIAPI api object initialization:
OpenAIAPI api = OpenAIAPI.ForAzure("opeanai-resource", "deployedEngine", "apikey");
CreatedUrl:
https://opeanai-resource.openai.azure.com/openai/deployments/deployedEngine)/{1}?api-version={0}
It adds a clos parenthesis to the resource engine, so I get this error:
The API deployment for the resource does not exist.
I guess the ApiVersion
{0}
and the completion{1}
are added when doing the requests, but are not showed in the UrlThe text was updated successfully, but these errors were encountered: