Skip to content
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

Fix gemini call params with pydantic 2.10.0 #708

Merged

Conversation

koxudaxi
Copy link
Collaborator

Fix: #677

@koxudaxi koxudaxi changed the base branch from main to release/v1.10 November 21, 2024 08:17
Copy link

codecov bot commented Nov 21, 2024

Codecov Report

All modified and coverable lines are covered by tests ✅

Project coverage is 100.00%. Comparing base (80eef5b) to head (a5dec7e).
Report is 2 commits behind head on release/v1.10.

Additional details and impacted files
@@               Coverage Diff               @@
##           release/v1.10      #708   +/-   ##
===============================================
  Coverage         100.00%   100.00%           
===============================================
  Files                398       398           
  Lines              13288     13298   +10     
===============================================
+ Hits               13288     13298   +10     
Flag Coverage Δ
tests 100.00% <100.00%> (ø)

Flags with carried forward coverage won't be shown. Click here to find out more.

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.


🚨 Try these New Features:

@willbakst willbakst merged commit 3f3cbe3 into release/v1.10 Nov 21, 2024
7 checks passed
@willbakst willbakst deleted the fix-gemini-call-params-with-pydantic-2.10.0 branch November 21, 2024 12:37
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Gemini calls failing - regression with pydantic >2.9.2
2 participants