-
Notifications
You must be signed in to change notification settings - Fork 3
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
OPENAI_BASE_URL instead of OPENAI_API_HOST #3
Comments
That is great you brought up this subject. Indeed, I have struggled to understand how to try and make this feature the most compatible across multiple service providers. I will check if we can make this naming convention more correct and also check if we can have |
It seems to be possible to correct both these issues without too many changes in the code of the script at this time... Even though we have updated the script to solve these issues today, we need some testing before release. I also found some more bugs (minor bugs) which are fixed now, however I need to test at least all the seven service provider configurations and functions before public release. I am not sure if I can create an account to use with Azure yet, but I will see it in the next few days so I can test your example server. In any case, I will do my best to make this script more compatible with other services out-of-the-box. |
It is github account. But you need to create special token. |
Doing some research, according to ref1 and ref2, baseUrl in our case would be exactly This means As I tested As our script targets OpenAI API version 1, I reckon we shall not be fixing this seemingly issue.. If unlikely the project decides to move on and support a future As for records, the script in the present version (v0.81.0) already works with GitHub Models. The syntax for it to work with GitHub Models would be:
The workaround (which already exists) for the script to work with a service provider which fails when
The Lastly, if the user creates a configuration file from the template ( The syntaxes above are described in the man page and in the Repository README.md. Therefore, it is unlikely that this issue ticket is going to be addresses because I don't see it as a real issue in our code context at the moment. Even though, I note that there is around ~4 times more code mentions of Most fortunately, I did find that the GitHub Models service is great and so I went ahead and implemented the command line option Just remember to have This is going to be available in version v0.81.1 which shall be released when I finish testing the new API service provider... |
Just in case you can help me, do you know any reliable way to dump GitHub Models as a list? I am using this for now:
And ALSO, when we try the
It returns:
|
curl -s https://models.inference.ai.azure.com/models \
-H "Authorization: Bearer github_pat_xxx" \
| jq .[].name
|
It's not about proper terminology. What I'm trying to convey is that most projects use https://api.openai.com/v1 as the configurable part that defines the API. There are real APIs that do not include the v1 part; some may use v2. This is not an issue, as all these cases can be addressed with a single option. Of course, there's no practical reason to customize the host and base separately. Therefore, the main reason for continuing to use the current API_HOST setting is compatibility, to avoid disrupting existing user setups.
Well, you are the boss. |
I really hope this project remains stable before |
It's not about api.openai.com compatibility. |
Right now
/v1
is part of ENDPOINT.But it is more common to have BASE_URL (or API_BASE) setting, which include
/v1
part as well:https://api.openai.com/v1
.Btw, this is so for GOOGLE_API_HOST, but not for others.
The reason: there are some services, which do not contain
/v1
part at allE.g.
https://models.inference.ai.azure.com/chat/completions
Ref: https://docs.github.com/en/github-models/prototyping-with-ai-models
The text was updated successfully, but these errors were encountered: