-
Notifications
You must be signed in to change notification settings - Fork 9
Make ai_model and ai_base_url actually do something #171
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
Merged
Merged
Changes from all commits
Commits
Show all changes
2 commits
Select commit
Hold shift + click to select a range
File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Oops, something went wrong.
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
/v1from the ruby-openai URI baseWith the bundled
ruby-openai8.3.0 client,uri_baseis the server root and the client adds its configured API version (v1) when constructing the chat endpoint. Now that this value is actually passed into the client, the default becomeshttps://api.openai.com/v1/v1/chat/completions, so ordinary OpenAI summary requests return 404; the documented custom URLs ending in/v1have the same problem. Use a root such ashttps://api.openai.com(and document custom roots accordingly), or explicitly account for the client's API-version handling.Useful? React with 👍 / 👎.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
🤖 Checked against the bundled gem (ruby-openai 8.3.0, pinned by sha in Gemfile.lock):
uriskips appendingapi_versionwhen the base already contains it —elsif @uri_base.include?(@api_version)inlib/openai/http.rb#uri. Verified against the real client, no stubs:No double
/v1in any configuration, including the documented custom URLs. The base-url spec in this PR was mock-based though, so the concern was fair that nothing pinned the gem's rule — 8da4147 adds two no-stub specs that exercise the real client's URI construction, so a future gem upgrade that changes the version-handling fails in CI instead of 404ing in production.