Repository navigation
Conversation
7 of 20 tasks
|
cancel() cleared syncInFlight unconditionally. Interrupting the executor does not stop the native syncBoth call, so a new sync could start while the cancelled one was still writing. Only clear the guard when shutdownNow() removed a task that never started, since only then will its completion callback never run.
0xbrayo
force-pushed
the
fix/sync-cancel-inflight-guard
branch
from
October 8, 2026 19:37
d0349d6 to
8eb1bec
Compare
If cancel() runs between publishing activeExecutor and submitting the task, shutdownNow() has nothing to return and the later execute() is rejected, so no completion callback ever cleared syncInFlight. Report the rejected submission through the callback, which releases it.
Member
Author
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Part of #333.
SyncInterface.cancel()(called when WorkManager stops aSyncWorker) cleared the sharedsyncInFlightguard unconditionally. Interrupting the executor thread does not stop the nativesyncBothcall, so the cancelled sync kept running while the next sync (from the Handler chain, the alarm, or a manual tap) was allowed to start alongside it, with both writing to the same sync directory and database.Change
cancel()clearssyncInFlightonly whenshutdownNow()returned a task that never started. Only then will that task's completion callback, which normally clears the guard, never run. That case was the original reason for clearing it here.Testing
./gradlew :mobile:testStandardDebugUnitTestpasses.SyncInterfaceloads the native aw-sync library, which isn't available to JVM unit tests, so this has no new unit test.