You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
"message": "Modernize FirebaseLibraryExtension (#6377)\n\nPer [b/270576405](https://b.corp.google.com/issues/270576405),\r\n\r\nThis migrates `FirebaseLibraryExtension` to Kotlin, and takes advantage\r\nof more modern gradle features (such as properties/conventions) to help\r\nwith build time and maintenance.\r\n\r\nThis also adds documentation for all the exposed properties and options\r\non `FirebaseLibraryExtension`.\r\n\r\nFuture `TODO`s have been left denoting possible future modernization\r\nefforts.\r\n\r\nThis PR also fixes the following:\r\n\r\n- [b/374137268](https://b.corp.google.com/issues/374137268) -> Migrate\r\nbuildSrc to spotless",
"message": "Add spotless support for *.gradle.kts files (#6399)\n\nThe more we cover by the formatter the better.\n\nThat being said, support for groovy is broken. I hit\nhttps://github.com/diffplug/spotless/issues/1922 when trying to use\ngroovyGradle formatting.",
"message": "Migrate crashlytics tests to JUnit4 (#6402)\n\nPer [b/375055031](https://b.corp.google.com/issues/375055031),\r\n\r\nThis performs various cleanups on the integration tests for crashlytics.\r\nThis should help narrow down flakey test behavior, and avoid any issues\r\nthat may arise from deprecated usages.\r\n\r\nNamely, this PR does the following:\r\n- Fully migrates all the tests to JUnit4. Some of them were still using\r\nJUnit3 behaviors.\r\n- Migrates `initMocks` to `openMocks`. There may have been broken\r\nbehavior from `initMocks` leakage.\r\n- Updates some existing `openMocks` to properly close. There may have\r\nbeen leakage into other tests, which could cause false positives.\r\n- Migrate `AndroidJunit4` usages to the new import. Some of the tests\r\nwere still using the old (deprecated) version.\r\n- Suppresses the receiver filter warning. This is a false positive as\r\nthe use-site only specifies two arguments. By suppressing the warning-\r\nit should help depollute our logs.",
"message": "Change WithinAppServiceConnection's ScheduledThreadPoolExecutor's con… (#6414)\n\n…figuration to avoid polling.\r\n\r\n* Changed WithinAppServiceConnection's ScheduledThreadPoolExecutor's\r\nconfiguration to allow the thread to stop polling after the timeout task\r\nhas been canceled.",
"message": "Modernize FirebaseLibraryExtension (#6377)\n\nPer [b/270576405](https://b.corp.google.com/issues/270576405),\r\n\r\nThis migrates `FirebaseLibraryExtension` to Kotlin, and takes advantage\r\nof more modern gradle features (such as properties/conventions) to help\r\nwith build time and maintenance.\r\n\r\nThis also adds documentation for all the exposed properties and options\r\non `FirebaseLibraryExtension`.\r\n\r\nFuture `TODO`s have been left denoting possible future modernization\r\nefforts.\r\n\r\nThis PR also fixes the following:\r\n\r\n- [b/374137268](https://b.corp.google.com/issues/374137268) -> Migrate\r\nbuildSrc to spotless",
"message": "Modernize FirebaseLibraryExtension (#6377)\n\nPer [b/270576405](https://b.corp.google.com/issues/270576405),\r\n\r\nThis migrates `FirebaseLibraryExtension` to Kotlin, and takes advantage\r\nof more modern gradle features (such as properties/conventions) to help\r\nwith build time and maintenance.\r\n\r\nThis also adds documentation for all the exposed properties and options\r\non `FirebaseLibraryExtension`.\r\n\r\nFuture `TODO`s have been left denoting possible future modernization\r\nefforts.\r\n\r\nThis PR also fixes the following:\r\n\r\n- [b/374137268](https://b.corp.google.com/issues/374137268) -> Migrate\r\nbuildSrc to spotless",
"message": "Modernize FirebaseLibraryExtension (#6377)\n\nPer [b/270576405](https://b.corp.google.com/issues/270576405),\r\n\r\nThis migrates `FirebaseLibraryExtension` to Kotlin, and takes advantage\r\nof more modern gradle features (such as properties/conventions) to help\r\nwith build time and maintenance.\r\n\r\nThis also adds documentation for all the exposed properties and options\r\non `FirebaseLibraryExtension`.\r\n\r\nFuture `TODO`s have been left denoting possible future modernization\r\nefforts.\r\n\r\nThis PR also fixes the following:\r\n\r\n- [b/374137268](https://b.corp.google.com/issues/374137268) -> Migrate\r\nbuildSrc to spotless",
"message": "Remove format from `double` helper function (#6432)\n\nWe can omit the format for the double-precision floating point type\r\n\r\nSee https://github.com/firebase/firebase-ios-sdk/pull/13990 for further\r\ncontext",
"message": "Improve error message for invalid locations (#6428)\n\nIf an invalid location is used when creating the `FirebaseVertexAI`\r\nobject, all requests will fail. The error returned is 404 and HTML\r\ncontent. The message as-is is not easy to read.\r\n\r\nThe new messaging points to the most likely reason for the\r\n404 (invalid location).",
"message": "Improved refdocs for Schema (#6420)\n\nThe improvements include:\r\n\r\n- Clarify that `integer` and `float` types are hints to the model, and\r\nthe returned data could potentially overflow the respective native\r\ntypes.\r\n- Include missing parameters for some of the functions.\r\n- Add examples for `enumerations` and `obj`.\r\n\r\n---------\r\n\r\nCo-authored-by: rachelsaunders <[email protected]>",
"message": "[vertexai] Include appcheck token unconditionally (#6409)\n\nThe app check backend can differentiate between apps that do not use\r\nappcheck at all, and those sending invalid data, by using a special\r\nplaceholder token when errors happen. We were previously not including\r\nthe token value in error cases, but we should.\r\n\r\n---------\r\n\r\nCo-authored-by: rachelsaunders <[email protected]>",
"message": "Fix vertexAI authorization header (#6400)\n\nThe header for authenticated request from vertex was using an invalid\r\nauthorization value\r\n\r\n---------\r\n\r\nCo-authored-by: rachelsaunders <[email protected]>",
"message": "Add spotless support for *.gradle.kts files (#6399)\n\nThe more we cover by the formatter the better.\n\nThat being said, support for groovy is broken. I hit\nhttps://github.com/diffplug/spotless/issues/1922 when trying to use\ngroovyGradle formatting.",
0 commit comments