-
Notifications
You must be signed in to change notification settings - Fork 578
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
Remove format from double
helper function
#6432
Conversation
We can omit the format for the double-precision floating point type
Release note changesThe following release notes were modified. Please ensure they look correct. Release Notesfirebase-vertexai### {{firebase_vertexai}} version 16.0.2 {: #vertex-ai_v16-0-2}
* {{fixed}} Improved error message when using an invalid location. GitHub [#6428](//github.com/firebase/firebase-android-sdk/issues/6428){: .external}
* {{fixed}} Fixed issue where Firebase App Check error tokens were unintentionally missing from the requests. GitHub [#6409](//github.com/firebase/firebase-android-sdk/issues/6409){: .external}
* {{fixed}} Clarified in the documentation that `Schema.integer` and `Schema.float` only provide hints to the model. GitHub [#6420](//github.com/firebase/firebase-android-sdk/issues/6420){: .external}
* {{fixed}} Fixed issue were `Schema.double` set the format parameter in `Schema`. GitHub [#6432](//github.com/firebase/firebase-android-sdk/issues/6432){: .external}
|
Vertex AI Mock Responses Check
|
Test Results 20 files - 34 20 suites - 34 14s ⏱️ - 1m 48s Results for commit a63d93d. ± Comparison against base commit 80019ca. This pull request removes 515 and adds 113 tests. Note that renamed tests count towards both.
♻️ This comment has been updated with latest results. |
double
helper functionsdouble
helper function
cc @andrewheard |
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 double the default? Is this behavior we should rely on?
e: I just saw the ios issue which helped provide context.
Although, isn't this an issue with the backend? Shouldn't it enforce it?
As documented in the kdoc, even if everything is working as expected, |
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.
SGTM. May be worth directly linking to andrew's PR in the PR desc for context/auditing
We can omit the format for the double-precision floating point type
See firebase/firebase-ios-sdk#13990 for further context