-
Notifications
You must be signed in to change notification settings - Fork 49
fix: watsonx and litellm parameter filtering #187
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
+126
−34
Merged
Changes from all commits
Commits
Show all changes
10 commits
Select commit
Hold shift + click to select a range
d33c6f4
fix: watsonx param filter
jakelorocco da44fd2
fix: litellm model options filtering and tests
jakelorocco f786f90
fix: change conftest to skip instead of fail qual tests on github
jakelorocco 4e1db49
fix: remove comment
jakelorocco 507a793
fix: test defaults
jakelorocco a647b74
test: fixes to litellm test
jakelorocco 8de5e2d
test:fix test defaults
jakelorocco e87f67b
Merge branch 'main' into jal/fix-watsonx-params
jakelorocco 8994f1b
Merge branch 'main' into jal/fix-watsonx-params
jakelorocco e7009be
Merge branch 'main' into jal/fix-watsonx-params
jakelorocco 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
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
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.
Is there a way to force LiteLLM to accept parameters that we should expose through our API as well?
Thinking of an analogy to the
--forceparameter from some linux commands.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.
We can set
drop_params=Falsein the call to the model. But I think this change is accomplishing what you are asking for withaccept parameters that we should expose through our API.Previously, we dropped all params that weren't "known" and "basic" openai parameters. Now, we let LiteLLM drop "known" but "unsupported" openai params. All other params get passed through transparently.
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.
And there are no false negatives - i.e. litellm filters out a parameter that the model understands but LiteLLM assumes it doesn't ?
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.
It's possible; I searched the LiteLLM github and the only errors I could find with drop_params is that it is too permissive (ie keeps parameters around that it shouldn't). We can disable
drop_paramsif you'd prefer to just pass through all parameters.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.
ok.. false positives are ok IMHO.