-
Notifications
You must be signed in to change notification settings - Fork 612
Store registered context for sync task unregistrations #6752
New issue
Have a question about this project? # for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “#”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? # 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. |
Coverage Report 1Affected Products
Test Logs |
Size Report 1Affected Products
Test Logs |
Test Results 64 files + 56 64 suites +56 6m 17s ⏱️ + 5m 58s Results for commit 678ad02. ± Comparison against base commit aa2bab8. This pull request removes 22 and adds 487 tests. Note that renamed tests count towards both.
♻️ This comment has been updated with latest results. |
For issue #6558, this is an attempt at fixing the IllegalArgumentException by ensuring that the context we use for registering the SyncTask is the same context we use to unregister the task. Race conditions dont seem like a culprit here since unregister is only triggered by the Receiver itself, which should be only executed synchronously on the main thread.
For issue #6558, this is an attempt at fixing the IllegalArgumentException by ensuring that the context we use for registering the SyncTask is the same context we use to unregister the task. Race conditions dont seem like a culprit here since unregister is only triggered by the Receiver itself, which should be only executed synchronously on the main thread.
New PR needed to fix CLA issue