-
Notifications
You must be signed in to change notification settings - Fork 2.8k
fix: Add support for required params #2212
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
Conversation
|
bump - @hangfei - can we get some eyes into this PR? |
|
@thiagosalvatore Thanks for creating this PR? Could you please provide a test plan for this change? More details can be found in the contributing guide. |
|
@xuanyang15 sure, I can do this. Just note that this is live for over 2 weeks in our fork because it wasn't approved/reviewed until today. PR updated with the test run |
|
Thank you @thiagosalvatore! Could you please fix the formatting issue? You can use the |
fixed @xuanyang15 |
Merge #2212 This PR closes issue #2202 ADK was not parsing the required attribute when using LiteLLM, letting the LLM decide what is required vs not, not respecting function definitions. ## Test Plan There's a fork of adk-python that is being running live for over 2 weeks in our production environment with millions of requests per day. Below you can find a screenshot of the unit tests passing. I've also added one change to the test cases to cover this scenario <img width="1904" height="483" alt="image" src="https://github.com/user-attachments/assets/5a6eb069-63ae-45a3-baca-6b01543f56fb" /> COPYBARA_INTEGRATE_REVIEW=#2212 from thiagosalvatore:main 7de4037 PiperOrigin-RevId: 797393698
This PR closes issue #2202
ADK was not parsing the required attribute when using LiteLLM, letting the LLM decide what is required vs not, not respecting function definitions.
Test Plan
There's a fork of adk-python that is being running live for over 2 weeks in our production environment with millions of requests per day.
Below you can find a screenshot of the unit tests passing. I've also added one change to the test cases to cover this scenario