-
Notifications
You must be signed in to change notification settings - Fork 615
Add headers to be able to track bidi usage #6939
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
📝 PRs merging into main branchOur main branch should always be in a releasable state. If you are working on a larger change, or if you don't want this change to see the light of the day just yet, consider using a feature branch first, and only merge into the main branch when the code complete and ready to be released. |
Generated by 🚫 Danger |
Coverage Report 1Affected ProductsNo changes between base commit (525f293) and merge commit (23dd81b).Test Logs |
Test Results 22 files - 1 034 22 suites - 1 034 34s ⏱️ - 34m 45s Results for commit a9c16ec. ± Comparison against base commit 525f293. This pull request removes 5874 tests.
♻️ This comment has been updated with latest results. |
firebase-ai/src/main/kotlin/com/google/firebase/ai/common/APIController.kt
Show resolved
Hide resolved
Size Report 1Affected Products
Test Logs |
Per [b/414829218](https://b.corp.google.com/issues/414829218), This ensures the Vertex AI SDK is properly aligned for the upcoming release. More specifically, this PR does the following: - Adds deprecation notices for all the public classes and interfaces, **besides** the root `FirebaseVertexAI` class and the relevant extension methods. - Updates the golden file version. - Adds the change from #6925 for working around invalid `SafetyRating`(s). - Adds a changelog entry that aligns with the deprecation notices. - Adds the changes from #6939 for tracking bidi usage. - Adds the changes from #6910 for aligning the bidi protos. --------- Co-authored-by: Rodrigo Lazo <[email protected]>
Originally we were not tracking bidi usage in android. This PR enables it by adding certain headers when the initial websocket connection is made. There was some refractoring done wrt to extract out the part which just adds the headers from the applyCommonConfiguration function