Skip to content

[Fireperf][AASA] send _experiment_app_start_ttid trace, controlled by RC flag #4114

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

Merged
merged 9 commits into from
Sep 28, 2022

Conversation

leotianlizhan
Copy link
Contributor

b/245947422
b/243540978

During startup, when we want to decide to record this trace or not, we only check disk cache for RC flag because RC is not initialized yet.

This RC flag will be saved to disk ONLY upon successful RC fetchAndActivate(). There's a problem with all other flags in that they are being saved to disk every time they are queried.

@google-oss-bot
Copy link
Contributor

google-oss-bot commented Sep 16, 2022

Coverage Report 1

Affected Products

  • firebase-perf

    Overall coverage changed from 71.22% (1d344e8) to 71.13% (6540c0f) by -0.08%.

    FilenameBase (1d344e8)Merge (6540c0f)Diff
    AppStartTrace.java86.54%85.19%-1.35%
    ConfigResolver.java97.38%93.19%-4.19%
    ConfigurationConstants.java99.25%97.86%-1.39%
    RemoteConfigManager.java92.86%91.79%-1.07%

Test Logs

  1. https://storage.googleapis.com/firebase-sdk-metric-reports/sYymXh8XBp.html

@github-actions
Copy link
Contributor

github-actions bot commented Sep 16, 2022

Unit Test Results

974 tests  +2   974 ✔️ +2   1m 55s ⏱️ +9s
  51 suites ±0       0 💤 ±0 
  51 files   ±0       0 ±0 

Results for commit 0ae206b. ± Comparison against base commit 6df92b9.

♻️ This comment has been updated with latest results.

@google-oss-bot
Copy link
Contributor

google-oss-bot commented Sep 16, 2022

Size Report 1

Affected Products

  • firebase-datatransport

    TypeBase (1d344e8)Merge (6540c0f)Diff
    apk (aggressive)136 kB132 kB-4.10 kB (-3.0%)
  • firebase-perf

    TypeBase (1d344e8)Merge (6540c0f)Diff
    aar309 kB311 kB+2.17 kB (+0.7%)
    apk (aggressive)1.03 MB1.03 MB+1.05 kB (+0.1%)
    apk (release)2.47 MB2.47 MB+920 B (+0.0%)

Test Logs

  1. https://storage.googleapis.com/firebase-sdk-metric-reports/x2XPx7rnjS.html

@leotianlizhan leotianlizhan changed the title [Fireperf][AASA] send _experiment_as_ttid trace, controlled by RC flag [Fireperf][AASA] send _experiment_app_start_ttid trace, controlled by RC flag Sep 22, 2022
Copy link
Contributor

@jeremyjiang-dev jeremyjiang-dev left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Looks good to me overall

public boolean getIsExperimentTTIDEnabled() {
// Order of precedence is:
// 1. If the value exists in Android Manifest, return this value.
// 2. Cannot read value from RC because it's not initalized yet
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

What does this precedence mean?

Copy link
Contributor Author

@leotianlizhan leotianlizhan Sep 27, 2022

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This is a comment in the same style as other flags if you look into the same file. Other flags has the order laid out like this, I just changed the 2nd step to "Cannot read from RC".

EDIT: after some thoughts, I added the RC check back. It doesn't hurt if RC is available, and doesn't hurt if RC isn't initialized because it would skip this step anyway.

@@ -342,6 +341,19 @@ protected void syncConfigValues(Map<String, FirebaseRemoteConfigValue> newlyFetc
allRcConfigMap.remove(existingKey);
}
}

// Save to device cache upon successful RC fetchAndActivate
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Can we detail more comments here since we are syncing a special config here in RC? Needs explanations for future references.

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Done

new ThreadPoolExecutor(
CORE_POOL_SIZE,
MAX_POOL_SIZE,
/* keepAliveTime= */ MAX_LATENCY_BEFORE_UI_INIT + 10,
TimeUnit.SECONDS,
new LinkedBlockingQueue<>(1)));
new LinkedBlockingQueue<>()));
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Do we know why they had a max count of 1 item in the queue earlier?

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

There was only 1 call to executorService.execute() before because we only had 1 app start trace.

@@ -228,12 +274,30 @@ public synchronized void onActivityResumed(Activity activity) {
// Log the app start trace in a non-main thread.
executorService.execute(this::logAppStartTrace);

if (isRegisteredForLifecycleCallbacks) {
if (!isExperimentTTIDEnabled && isRegisteredForLifecycleCallbacks) {
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

What happens if the flag dynamically changes from No to YES (or) vice versa? Would that cause a situation where we try to unregister for callbacks when we have not registered or the other way about?

Copy link
Contributor Author

@leotianlizhan leotianlizhan Sep 27, 2022

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Good question! Since this flag is only read once in the beginning of AppStartTrace#onActivityResumed, it's not a problem.

Scenario 1: experiment disabled, an activity resumed, experiment enabled, another activity resumed.

After the first resume, the unregistering would be called, so the 2nd activity resume would not do anything. TTID isn't recorded for this app start, it will only start working next app start.

Scenario 2: experiment enabled, an activity resumed, experiment disabled, another activity resumed.

After the first resume, the AppStartTrace.onResume variable would be set, so even if the 2nd activity resume triggers, nothing happens because this method will return immediately without sending anything else.

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Sounds good.

For the first scenario - I assume that experiment is disabled?

In the second scenario - I assume that would mean experiment is enabled?

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Yes, these scenarios show what happens if the app starts with 1 state, then changes after app start.


metric.addSubtraces(subtrace).addPerfSessions(this.startSession.build());

transportManager.log(metric.build(), ApplicationProcessState.FOREGROUND_BACKGROUND);
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Why FOREGROUND_BACKGROUND?

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

_app_start is FOREGROUND_BACKGROUND so I am just following the same behavior.

@leotianlizhan
Copy link
Contributor Author

Health Metrics / Coverage (push) fails due to firestorage test failures, so we can merge.

@leotianlizhan leotianlizhan merged commit 6300987 into master Sep 28, 2022
@leotianlizhan leotianlizhan deleted the experiment_ttid branch September 28, 2022 01:38
lfkellogg added a commit that referenced this pull request Oct 26, 2022
* Deflake firebase_common HeartBeat tests. (#4083)

The tests relied on `TestOnCompleteListener` that was not safe to call
more than once since it was based on a count down latch. So reusing it
multiple times would cause await() to return immediately.

This change makes it so that a new latch is created for every await()
call, making all await() calls work.

Fixes: http://b/245956774

* Add Javadoc support to the DackkaPlugin (#4082)

* Add util method for copying directories

* Add javadoc support to our dackka plugin

* Remove the extension check on fromDirectory

* Add a note about cache compliance and the javadoc task

* Add reference to kotlin stdlib package list (#4093)

* Add appcheck-ktx to bom config (#4081)

* Removing getRunningAppProcesses since the process_name isn't used (#4057)

* Fix Documentation classpath (#4099)

b/241795594

* Add projectSpecificSources back to the DackkaPlugin (#4110)

* Added extra method for TaskProviders

* Added specificSources method back

* Revert to dependsOn for docstubs dep

* Revamp test harness for macrobenchmark tests (#4071)

* Fix dependabot security alerts (#4123)

* Make firesite transform cacheable (#4124)

* add coroutines-play-services as a transitive dep to firebase-common-ktx (#4044)

* add kotlinx-coroutines-play-services as a transitive dep to firebase-common-ktx

* Update to Coroutines 1.6.4

* database-ktx: add callbackFlow for eventlisteners (#4012)

* add callbackFlow for RTDB's ValueEventListener

* add callbackFlow for RTDB's ChildEventListener

* delegate trySendBlocking to DefaultRunLoop

* add group to ktx.gradle

* update api.txt file

* Update released versions (#4135)

* Upgrade dackkaConfig (#4141)

* Add names to all Firebase components (#4117)

* Add appcheck's ktx artifact back to package list file (#4142)

* Add strict mode testing in firebase-messaging (#4095)

* Add gralde property to instrument Fireperf E2E test (#4144)

The perf gradle PR is #334 in the gradle repo.

b/246802885

* Resolve StrictMode violation in App Check. (#4085)

* Resolve StrictMode violation in App Check.

* Attempt to fix some tests.

* Fix unit tests.

* Make `retrieveStoredAppCheckTokenInBackground` private instead of package-private.

* Move listener invocations back to the main thread while keeping disk write on background thread.

* Refactor to use lambda syntax.

* Implemented exponential backoff and max retry with resumable uploads (#4087)

* storage-ktx: add callbackFlow for upload/download progress (#4139)

* add kotlin flows to storage

* update api.txt file

* add group to storage/ktx.gradle

* Make a best effort attempt to flush reports at crash time (#4112)

This should allow us to upload reports for start-up crashes.

* Public Count (#4130)

* Public Count

* Disable prod testing

* Long to long

* Api.txt

* Backfill changelog

* Add PR

* Fix assertEquals error

* Re-write API javadocs for COUNT API (#4143)

Co-authored-by: Denver Coneybeare <[email protected]>

* [Fireperf][AASA] send `_experiment_app_start_ttid` trace, controlled by RC flag (#4114)

* log _experiment_as_ttid

* send event and RRC mitigation

* add RC wip

* modified save to cache when RC fetches

* dev-app manifest override

* unit test for RCc cache saving

* better name and comments

* better formatting remoteconfigmanagertest

* better comments and added local RC lookup back

* Specify unique ref tags in Dackka output (#4149)

* Add util methods for gradle projects

* Disable Javadoc generation on empty projects

* Fix ref path generation in Dackka output

* Add documentation for util methods

* Update the DackkaPlugin docs

* Reduced path to relative from tenant

* Reduced ref head path even more

* Fixed ref tag path to working solution

* Disabled publishJavadoc by default for tests

It should be enabled explicitly when being tested anyhow, and causes issues otherwise. Instead of disabling it for the tests that don't need it- this is much quicker and easier to manager.

* Add strict mode tests to inappmessaging and inappmessaging-display (#4136)

* Fix strict mode violations for appcheck (#4148)

* Fix strict mode violations for appcheck

* Formatting

* Add copyright header

* Populate SDKs changelog files (#4070)

* first try seeding changelogs

* Added unreleased section to CHANGELOG

* Fix empty lines between sections

* Add missing entries for abt

* Update data to include latest releases

* Update CHANGELOG.md

* Add missing line in unreleased section for perf.

* Enable CHANGELOG check globally (#4084)

* Enable CHANGELOG check globally

* Simplify conditional.

* Enable COUNT integration tests, now that backend support has rolled out (#4163)

* Remove separation of kotlin directories in dackka (#4166)

* Deprecate App Check SafetyNet SDK (#4187)

* Add `@Deprecated` annotations to Firebase App Check SafetyNet SDK public API.

* Add `@deprecated` tag in the Javadoc as well.

* Remove stale entries from Unreleased section. (#4185)

* Assign ConfigContainer Builder return values. (#4194)

* update bom (#4155)

* update bom

* update

* update

* feat(perf-ktx): add trace(name, block) extension function (#4180)

* Remove smoke test for app indexing (#4219)

App Indexing is deprecated starting BoM 31.0.0 .

https://firebase.google.com/support/release-notes/android#bom_v31-0-0

* Bump Robolectric to 4.9 (#4161)

* Add plexus-utils for firebase-database tests

Looks like firebase-database tests use plexus-utils dependency of
Robolectric directly. But this dependency was removed by Robolectric. So
this CL adds plexus-utils explictly for firebase-database tests.

Signed-off-by: utzcoz <[email protected]>

* Bump Robolectric to 4.9

1. Use legacy LooperMode for tests explicitly, because recent
   Robolectric releases switch to use PAUSED mode default. Before these
   tests migrate to PAUSED mode, they use LEGACY mode to pass tests.
2. Migrate Assert.assertThat to Truth.assertThat to avoid using removed
   APIs.
3. All build.gradle use the same robolectricVersion except
   transport-backend-cct because Robolectric 4.8+ has compatibility
   problem for TelephonyManager with low compile/targetSdkversion.
   To keep httpclient compatibility, transport-backend-ccts continues to
   use Robolectric 4.3.1.
4. Remove unused exclude protobuf-java from Robolectric.
5. Add necessary protobuf-lite dependency on classpath for
   some ktx modules' tests.

Signed-off-by: utzcoz <[email protected]>

Signed-off-by: utzcoz <[email protected]>

* return exception if modelname is empty (#4226)

* Add "create release PR" github action (#4236)

This implementation:

- Creates the base branch (name is based in user input)
- Creates the release branch (name is based in user input)
- Creates the release.cfg file in the release branch without adding
  any SDK (module) to it.

It can create the branches based on any existing branch of the repo.

* Sync spec tests from web SDK to Android SDK (#4230)

* Update versions (#4238)

* Update versions

* Exclude .github dir from `firebaseContinuousIntegration` paths (#4239)

* Performing IN expansion (#4221)

* WIP: `in` expansion.

* Add composite filter in-expansion test.

* Fix formatting.

* Run in-expansion as part of DNF computation and add tests.

* Add test with nested IN filters with CSI.

* Add tests for other cases.

* typo fix (#4237)

* Firestore: Add test that verifies count query error message when missing index (#4232)

* refactor(functions): update firebase-iid to 21.1.0 (#4225)

* refactor(functions): update firebase-iid to 21.1.0

* Update CHANGELOG.md

* Update CHANGELOG.md

* bump firebase-iid-interop to 17.1.0

* exclude firebase-components from firebase-iid dependency

Signed-off-by: utzcoz <[email protected]>
Co-authored-by: Vladimir Kryachko <[email protected]>
Co-authored-by: Daymon <[email protected]>
Co-authored-by: Raymond Lam <[email protected]>
Co-authored-by: Yifan Yang <[email protected]>
Co-authored-by: Rosário Pereira Fernandes <[email protected]>
Co-authored-by: emilypgoogle <[email protected]>
Co-authored-by: Jeremy Jiang <[email protected]>
Co-authored-by: Rosalyn Tan <[email protected]>
Co-authored-by: Maneesh Tewani <[email protected]>
Co-authored-by: Matthew Robertson <[email protected]>
Co-authored-by: wu-hui <[email protected]>
Co-authored-by: Denver Coneybeare <[email protected]>
Co-authored-by: Leo Zhan <[email protected]>
Co-authored-by: Rodrigo Lazo <[email protected]>
Co-authored-by: Dana Silver <[email protected]>
Co-authored-by: Vinay Guthal <[email protected]>
Co-authored-by: utzcoz <[email protected]>
Co-authored-by: argzdev <[email protected]>
Co-authored-by: Mila <[email protected]>
Co-authored-by: Ehsan <[email protected]>
Co-authored-by: cherylEnkidu <[email protected]>
lfkellogg added a commit that referenced this pull request Oct 27, 2022
* Minor updates to the App Distribution test app. (#4088)

* Update various versions (#4090)

* Updated various versions (dependencies and SDK to fix Android resource linking failure (AAPT: error: resource android:attr/lStar not found.)

* Update compileSdk/targetSdkVersion from 31 to 33

* Update with latest changes from master (#4091)

* Deflake firebase_common HeartBeat tests. (#4083)

The tests relied on `TestOnCompleteListener` that was not safe to call
more than once since it was based on a count down latch. So reusing it
multiple times would cause await() to return immediately.

This change makes it so that a new latch is created for every await()
call, making all await() calls work.

Fixes: http://b/245956774

* Add Javadoc support to the DackkaPlugin (#4082)

* Add util method for copying directories

* Add javadoc support to our dackka plugin

* Remove the extension check on fromDirectory

* Add a note about cache compliance and the javadoc task

* Add reference to kotlin stdlib package list (#4093)

Co-authored-by: Vladimir Kryachko <[email protected]>
Co-authored-by: Daymon <[email protected]>

* Resolve strict mode violations in firebase-appdistribution (#4092)

* merge master into fad/next (#4102)

* Deflake firebase_common HeartBeat tests. (#4083)

The tests relied on `TestOnCompleteListener` that was not safe to call
more than once since it was based on a count down latch. So reusing it
multiple times would cause await() to return immediately.

This change makes it so that a new latch is created for every await()
call, making all await() calls work.

Fixes: http://b/245956774

* Add Javadoc support to the DackkaPlugin (#4082)

* Add util method for copying directories

* Add javadoc support to our dackka plugin

* Remove the extension check on fromDirectory

* Add a note about cache compliance and the javadoc task

* Add reference to kotlin stdlib package list (#4093)

Co-authored-by: Vladimir Kryachko <[email protected]>
Co-authored-by: Daymon <[email protected]>

* Remove `release` field. (#4174)

* Merge changes from master into fad/next (#4199)

* Merge latest master into fad/next (#4247)

* Deflake firebase_common HeartBeat tests. (#4083)

The tests relied on `TestOnCompleteListener` that was not safe to call
more than once since it was based on a count down latch. So reusing it
multiple times would cause await() to return immediately.

This change makes it so that a new latch is created for every await()
call, making all await() calls work.

Fixes: http://b/245956774

* Add Javadoc support to the DackkaPlugin (#4082)

* Add util method for copying directories

* Add javadoc support to our dackka plugin

* Remove the extension check on fromDirectory

* Add a note about cache compliance and the javadoc task

* Add reference to kotlin stdlib package list (#4093)

* Add appcheck-ktx to bom config (#4081)

* Removing getRunningAppProcesses since the process_name isn't used (#4057)

* Fix Documentation classpath (#4099)

b/241795594

* Add projectSpecificSources back to the DackkaPlugin (#4110)

* Added extra method for TaskProviders

* Added specificSources method back

* Revert to dependsOn for docstubs dep

* Revamp test harness for macrobenchmark tests (#4071)

* Fix dependabot security alerts (#4123)

* Make firesite transform cacheable (#4124)

* add coroutines-play-services as a transitive dep to firebase-common-ktx (#4044)

* add kotlinx-coroutines-play-services as a transitive dep to firebase-common-ktx

* Update to Coroutines 1.6.4

* database-ktx: add callbackFlow for eventlisteners (#4012)

* add callbackFlow for RTDB's ValueEventListener

* add callbackFlow for RTDB's ChildEventListener

* delegate trySendBlocking to DefaultRunLoop

* add group to ktx.gradle

* update api.txt file

* Update released versions (#4135)

* Upgrade dackkaConfig (#4141)

* Add names to all Firebase components (#4117)

* Add appcheck's ktx artifact back to package list file (#4142)

* Add strict mode testing in firebase-messaging (#4095)

* Add gralde property to instrument Fireperf E2E test (#4144)

The perf gradle PR is #334 in the gradle repo.

b/246802885

* Resolve StrictMode violation in App Check. (#4085)

* Resolve StrictMode violation in App Check.

* Attempt to fix some tests.

* Fix unit tests.

* Make `retrieveStoredAppCheckTokenInBackground` private instead of package-private.

* Move listener invocations back to the main thread while keeping disk write on background thread.

* Refactor to use lambda syntax.

* Implemented exponential backoff and max retry with resumable uploads (#4087)

* storage-ktx: add callbackFlow for upload/download progress (#4139)

* add kotlin flows to storage

* update api.txt file

* add group to storage/ktx.gradle

* Make a best effort attempt to flush reports at crash time (#4112)

This should allow us to upload reports for start-up crashes.

* Public Count (#4130)

* Public Count

* Disable prod testing

* Long to long

* Api.txt

* Backfill changelog

* Add PR

* Fix assertEquals error

* Re-write API javadocs for COUNT API (#4143)

Co-authored-by: Denver Coneybeare <[email protected]>

* [Fireperf][AASA] send `_experiment_app_start_ttid` trace, controlled by RC flag (#4114)

* log _experiment_as_ttid

* send event and RRC mitigation

* add RC wip

* modified save to cache when RC fetches

* dev-app manifest override

* unit test for RCc cache saving

* better name and comments

* better formatting remoteconfigmanagertest

* better comments and added local RC lookup back

* Specify unique ref tags in Dackka output (#4149)

* Add util methods for gradle projects

* Disable Javadoc generation on empty projects

* Fix ref path generation in Dackka output

* Add documentation for util methods

* Update the DackkaPlugin docs

* Reduced path to relative from tenant

* Reduced ref head path even more

* Fixed ref tag path to working solution

* Disabled publishJavadoc by default for tests

It should be enabled explicitly when being tested anyhow, and causes issues otherwise. Instead of disabling it for the tests that don't need it- this is much quicker and easier to manager.

* Add strict mode tests to inappmessaging and inappmessaging-display (#4136)

* Fix strict mode violations for appcheck (#4148)

* Fix strict mode violations for appcheck

* Formatting

* Add copyright header

* Populate SDKs changelog files (#4070)

* first try seeding changelogs

* Added unreleased section to CHANGELOG

* Fix empty lines between sections

* Add missing entries for abt

* Update data to include latest releases

* Update CHANGELOG.md

* Add missing line in unreleased section for perf.

* Enable CHANGELOG check globally (#4084)

* Enable CHANGELOG check globally

* Simplify conditional.

* Enable COUNT integration tests, now that backend support has rolled out (#4163)

* Remove separation of kotlin directories in dackka (#4166)

* Deprecate App Check SafetyNet SDK (#4187)

* Add `@Deprecated` annotations to Firebase App Check SafetyNet SDK public API.

* Add `@deprecated` tag in the Javadoc as well.

* Remove stale entries from Unreleased section. (#4185)

* Assign ConfigContainer Builder return values. (#4194)

* update bom (#4155)

* update bom

* update

* update

* feat(perf-ktx): add trace(name, block) extension function (#4180)

* Remove smoke test for app indexing (#4219)

App Indexing is deprecated starting BoM 31.0.0 .

https://firebase.google.com/support/release-notes/android#bom_v31-0-0

* Bump Robolectric to 4.9 (#4161)

* Add plexus-utils for firebase-database tests

Looks like firebase-database tests use plexus-utils dependency of
Robolectric directly. But this dependency was removed by Robolectric. So
this CL adds plexus-utils explictly for firebase-database tests.

Signed-off-by: utzcoz <[email protected]>

* Bump Robolectric to 4.9

1. Use legacy LooperMode for tests explicitly, because recent
   Robolectric releases switch to use PAUSED mode default. Before these
   tests migrate to PAUSED mode, they use LEGACY mode to pass tests.
2. Migrate Assert.assertThat to Truth.assertThat to avoid using removed
   APIs.
3. All build.gradle use the same robolectricVersion except
   transport-backend-cct because Robolectric 4.8+ has compatibility
   problem for TelephonyManager with low compile/targetSdkversion.
   To keep httpclient compatibility, transport-backend-ccts continues to
   use Robolectric 4.3.1.
4. Remove unused exclude protobuf-java from Robolectric.
5. Add necessary protobuf-lite dependency on classpath for
   some ktx modules' tests.

Signed-off-by: utzcoz <[email protected]>

Signed-off-by: utzcoz <[email protected]>

* return exception if modelname is empty (#4226)

* Add "create release PR" github action (#4236)

This implementation:

- Creates the base branch (name is based in user input)
- Creates the release branch (name is based in user input)
- Creates the release.cfg file in the release branch without adding
  any SDK (module) to it.

It can create the branches based on any existing branch of the repo.

* Sync spec tests from web SDK to Android SDK (#4230)

* Update versions (#4238)

* Update versions

* Exclude .github dir from `firebaseContinuousIntegration` paths (#4239)

* Performing IN expansion (#4221)

* WIP: `in` expansion.

* Add composite filter in-expansion test.

* Fix formatting.

* Run in-expansion as part of DNF computation and add tests.

* Add test with nested IN filters with CSI.

* Add tests for other cases.

* typo fix (#4237)

* Firestore: Add test that verifies count query error message when missing index (#4232)

* refactor(functions): update firebase-iid to 21.1.0 (#4225)

* refactor(functions): update firebase-iid to 21.1.0

* Update CHANGELOG.md

* Update CHANGELOG.md

* bump firebase-iid-interop to 17.1.0

* exclude firebase-components from firebase-iid dependency

Signed-off-by: utzcoz <[email protected]>
Co-authored-by: Vladimir Kryachko <[email protected]>
Co-authored-by: Daymon <[email protected]>
Co-authored-by: Raymond Lam <[email protected]>
Co-authored-by: Yifan Yang <[email protected]>
Co-authored-by: Rosário Pereira Fernandes <[email protected]>
Co-authored-by: emilypgoogle <[email protected]>
Co-authored-by: Jeremy Jiang <[email protected]>
Co-authored-by: Rosalyn Tan <[email protected]>
Co-authored-by: Maneesh Tewani <[email protected]>
Co-authored-by: Matthew Robertson <[email protected]>
Co-authored-by: wu-hui <[email protected]>
Co-authored-by: Denver Coneybeare <[email protected]>
Co-authored-by: Leo Zhan <[email protected]>
Co-authored-by: Rodrigo Lazo <[email protected]>
Co-authored-by: Dana Silver <[email protected]>
Co-authored-by: Vinay Guthal <[email protected]>
Co-authored-by: utzcoz <[email protected]>
Co-authored-by: argzdev <[email protected]>
Co-authored-by: Mila <[email protected]>
Co-authored-by: Ehsan <[email protected]>
Co-authored-by: cherylEnkidu <[email protected]>

* Fix ImageUtils test after robolectric update

* Remove extra member initialization in test app

* Ignore flaky test

Signed-off-by: utzcoz <[email protected]>
Co-authored-by: Kai Bolay <[email protected]>
Co-authored-by: Vladimir Kryachko <[email protected]>
Co-authored-by: Daymon <[email protected]>
Co-authored-by: emilypgoogle <[email protected]>
Co-authored-by: Raymond Lam <[email protected]>
Co-authored-by: Yifan Yang <[email protected]>
Co-authored-by: Rosário Pereira Fernandes <[email protected]>
Co-authored-by: Jeremy Jiang <[email protected]>
Co-authored-by: Rosalyn Tan <[email protected]>
Co-authored-by: Maneesh Tewani <[email protected]>
Co-authored-by: Matthew Robertson <[email protected]>
Co-authored-by: wu-hui <[email protected]>
Co-authored-by: Denver Coneybeare <[email protected]>
Co-authored-by: Leo Zhan <[email protected]>
Co-authored-by: Rodrigo Lazo <[email protected]>
Co-authored-by: Dana Silver <[email protected]>
Co-authored-by: Vinay Guthal <[email protected]>
Co-authored-by: utzcoz <[email protected]>
Co-authored-by: argzdev <[email protected]>
Co-authored-by: Mila <[email protected]>
Co-authored-by: Ehsan <[email protected]>
Co-authored-by: cherylEnkidu <[email protected]>
@firebase firebase locked and limited conversation to collaborators Oct 29, 2022
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
Projects
None yet
Development

Successfully merging this pull request may close these issues.

5 participants