Skip to:
Calling `cancel()` on the context to end the flow, causes `runBlocking` the throw an interrupted exception, and thus the failure of the worker.
Moving most of the logic from the `collect` call, to a `map` and introducing a `takeWhile` is more elegant, and does not generate the exception
Build couchbase-lite-android-3.2.0-3 contains couchbase-lite-java-ee-root commit 39f7339 with commit message:: WorkManager Replication tests and fixes (#97)
Build couchbase-lite-android-3.2.0-3 contains couchbase-lite-java-common commit 40ee6df with commit message:: WorkManager Replication tests and fixes (#166)
Build couchbase-lite-android-3.2.0-3 contains couchbase-lite-java-ce commit 4a0fe6c with commit message:: WorkManager Replication tests and fixes
Build couchbase-lite-java-3.2.0-3 contains couchbase-lite-java-ee-root commit 39f7339 with commit message:: WorkManager Replication tests and fixes (#97)
Build couchbase-lite-java-3.2.0-3 contains couchbase-lite-java-common commit 40ee6df with commit message:: WorkManager Replication tests and fixes (#166)
Calling `cancel()` on the context to end the flow, causes `runBlocking` the throw an interrupted exception, and thus the failure of the worker.
Moving most of the logic from the `collect` call, to a `map` and introducing a `takeWhile` is more elegant, and does not generate the exception