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

Azure openai自定义模型 #1952

Closed
pei92 opened this issue Apr 10, 2024 · 4 comments · Fixed by #1916
Closed

Azure openai自定义模型 #1952

pei92 opened this issue Apr 10, 2024 · 4 comments · Fixed by #1916
Labels
🌠 Feature Request New feature or request | 特性与建议 released

Comments

@pei92
Copy link

pei92 commented Apr 10, 2024

🥰 需求描述

目前的Azure_url变量,填的值为域名(https://xxx.openai.azure.com)。
Azure的每个区域的模型配额不同,例如可能没有gpt-4-preview。建议url加上用户自己部署的模型名称。

🧐 解决方案

建议azure_proxy_url变量的值为:https://xxx.openai.azure.com/openai /deployments/{model}

📝 补充信息

No response

@pei92 pei92 added the 🌠 Feature Request New feature or request | 特性与建议 label Apr 10, 2024
@lobehubbot
Copy link
Member

Bot detected the issue body's language is not English, translate it automatically. 👯👭🏻🧑‍🤝‍🧑👫🧑🏿‍🤝‍🧑🏻👩🏾‍🤝‍👨🏿👬🏿


🥰 Description of requirements

The current Azure_url variable is filled with the domain name (https://xxx.openai.azure.com).
Azure has different model quotas per region, for example there may not be gpt-4-preview. It is recommended that the URL be added with the name of the model deployed by the user.

🧐 Solution

It is recommended that the value of the azure_proxy_url variable is: https://xxx.openai.azure.com/openai /deployments/{model}

📝 Supplementary information

No response

@lobehubbot
Copy link
Member

👀 @pei92

Thank you for raising an issue. We will investigate into the matter and get back to you as soon as possible.
Please make sure you have given us as much context as possible.
非常感谢您提交 issue。我们会尽快调查此事,并尽快回复您。 请确保您已经提供了尽可能多的背景信息。

@lobehubbot
Copy link
Member

@pei92

This issue is closed, If you have any questions, you can comment and reply.
此问题已经关闭。如果您有任何问题,可以留言并回复。

@lobehubbot
Copy link
Member

🎉 This issue has been resolved in version 0.147.0 🎉

The release is available on:

Your semantic-release bot 📦🚀

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
🌠 Feature Request New feature or request | 特性与建议 released
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants