Repository navigation
fix(llm): prevent duplicate version segments in API paths - #528
Merged
stefan-ernst merged 1 commit intoNov 17, 2026
Merged
Conversation
|
All contributors have signed the CLA ✍️ ✅ |
Contributor
Author
|
I have read the CLA Document and I hereby sign the CLA |
Contributor
|
Thanks a lot for the fix! Will ship it with 0.9.5 |
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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Problem
The Local / Custom LLM endpoint prepends
/v1/modelsfor base URL that doesn't end with/v1. This conflicts with some endpoints likehttps://<host>/v1/unified-modelwhich has/modelsendpoint athttps://<host>/v1/unified-model/models.Fix
Added a new function
url.dropDuplicateVersionPrefixwhich removes a leading version segment (/v1,/v1beta, ...) from apiPath when the base URL already carries that same version as one of its own path segments.