-
Notifications
You must be signed in to change notification settings - Fork 2.2k
fix: #3065 LiteLLM Model Override Not Working with llm_request.model #3066
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
base: main
Are you sure you want to change the base?
Conversation
Summary of ChangesHello @ayam04, I'm Gemini Code Assist1! I'm currently reviewing this pull request and will post my feedback shortly. In the meantime, here's a summary to help you and other reviewers quickly get up to speed! This pull request addresses a critical bug in the LiteLLM integration that previously prevented the dynamic overriding of models during runtime. By adjusting the model selection logic, the system now correctly respects model specifications within Highlights
Using Gemini Code AssistThe full guide for Gemini Code Assist can be found on our documentation page, here are some quick tips. Invoking Gemini You can request assistance from Gemini at any point by creating a comment using either
Customization To customize Gemini Code Assist for GitHub experience, repository maintainers can create a configuration file and/or provide a custom code review style guide (such as PEP-8 for Python) by creating and adding files to a Limitations & Feedback Gemini Code Assist may make mistakes. Please leave feedback on any instances where its feedback is incorrect or counter productive. You can react with 👍 and 👎 on @gemini-code-assist comments. If you're interested in giving your feedback about your experience with Gemini Code Assist for Github and other Google products, sign up here. You can also get AI-powered code generation, chat, as well as code reviews directly in the IDE at no cost with the Gemini Code Assist IDE Extension. Footnotes
|
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.
Code Review
This pull request correctly fixes an issue where the model override in LlmRequest was being ignored by LiteLlm. The change to prioritize llm_request.model over self.model is a clean and effective solution. The addition of new tests to cover both the override and fallback scenarios is great. I've added one suggestion to improve the new test code by simplifying it, which will make it more focused and maintainable.
|
hi @seanzhougoogle, would u be reviewing the PR? |
|
@GWeale conflicts resolved |
…tent async method in LiteLLM Merge #3066 Close #3065 Co-authored-by: Raman Mangla <[email protected]> PiperOrigin-RevId: 825880794
|
Hi thank you for this change can you fix the pyink, and resolve merge conflicts. |
|
Sure, updated the branch,. You can review it now. |
fix: #3065
Bug
LiteLlm.generate_content_asyncalways usedself.model, ignoring the model specified inllm_request.modelFix
"model": self.modelto"model": llm_request.model or self.modelllm_request.modelwhen set, with fallback toself.modelwhenNoneChanges
test_generate_content_async_with_model_override- verifies override workstest_generate_content_async_without_model_override- verifies fallback worksTesting Plan
test_generate_content_async_with_model_overridellm_request.modelis set to a different value, it overridesself.modelmodel="test_model"model="overridden_model""overridden_model"test_generate_content_async_without_model_overridellm_request.modelisNone, it falls back toself.modelmodel="test_model"model=None"test_model"(the fallback)Test Results
Coverage
llm_requestis usedself.modelis used whenllm_request.modelisNoneManual Testing
The fix enables the following use case (tested via agent callbacks):
Use Case Enabled