commit | 90c1617d55fc82e43926802fc499c5ca1e0ad032 | [log] [tgz] |
---|---|---|
author | Terry Wang <tytytyww@google.com> | Thu Oct 19 16:31:26 2023 -0700 |
committer | Terry Wang <tytytyww@google.com> | Tue Oct 24 13:12:50 2023 -0700 |
tree | 4185d125c06ee1b5fe3fd1d18515adf212abe13d | |
parent | 5ba6fd9f4d35879f1f567eeb052fa2eb33619e14 [diff] |
Fix flaky test testAddObserver. The test set a schema and put a document to db. We should have 1 schema notification 1 document notification. However we keep receiving 2 document notifications. Both SetSchema() and Put() will trigger dispatch notification jobs. The first dispatch notification job triggered by SetSchema will be scheduled in the executor. And before it get executed, the document change is made and got picked up by the first dispatch notification job. This shouldn't happened since we copy and clean the pending change before schedule the dispatch notification job in the executor. However, we only copy and clean non-empty changes, but new change could be added to the empty-change between we schedule the job and the execution. This change also clean the observer in the end of tests. Bug: 292743317 Test: https://atp.googleplex.com/test_runs/348014056 Change-Id: I63a649ebe8acae82f7e3c34a3beeea63eb4108f4
Jetpack is a suite of libraries, tools, and guidance to help developers write high-quality apps easier. These components help you follow best practices, free you from writing boilerplate code, and simplify complex tasks, so you can focus on the code you care about.
Jetpack comprises the androidx.*
package libraries, unbundled from the platform APIs. This means that it offers backward compatibility and is updated more frequently than the Android platform, making sure you always have access to the latest and greatest versions of the Jetpack components.
Our official AARs and JARs binaries are distributed through Google Maven.
You can learn more about using it from Android Jetpack landing page.
For contributions via GitHub, see the GitHub Contribution Guide.
Note: The contributions workflow via GitHub is currently experimental - only contributions to the following projects are being accepted at this time:
When contributing to Jetpack, follow the code review etiquette.
We are not currently accepting new modules.
Head over to the onboarding docs to learn more about getting set up and the development workflow!
Our continuous integration system builds all in progress (and potentially unstable) libraries as new changes are merged. You can manually download these AARs and JARs for your experimentation.
Before uploading your first contribution, you will need setup a password and agree to the contribution agreement:
Generate a HTTPS password: https://android-review.googlesource.com/new-password
Agree to the Google Contributor Licenses Agreement: https://android-review.googlesource.com/settings/new-agreement
AndroidX uses git to store all the binary Gradle dependencies. They are stored in prebuilts/androidx/internal
and prebuilts/androidx/external
directories in your checkout. All the dependencies in these directories are also available from google()
, or mavenCentral()
. We store copies of these dependencies to have hermetic builds. You can pull in a new dependency using our importMaven tool.