IssueTracker

Project: platform/frameworks/support
Branch: androidx-master-dev

commit b90079595f33f58fece04026a97faa0d243acdb1
Author: Yuichi Araki <yaraki@google.com>
Date:   Wed Sep 18 16:55:49 2019

    Change the way to detect mismatch between POJO and query
   
    This fixes cursor mismatch warnings with expandProjection.
   
    Bug: 140759491
    Test: QueryMethodProcessorTest
    Change-Id: I7659002e5e0d1ef60fc1af2a625c0c36da0664d8

M       room/compiler/src/main/kotlin/androidx/room/processor/QueryMethodProcessor.kt
M       room/compiler/src/main/kotlin/androidx/room/solver/TypeAdapterStore.kt
M       room/compiler/src/main/kotlin/androidx/room/solver/query/result/PojoRowAdapter.kt
M       room/compiler/src/test/kotlin/androidx/room/processor/QueryMethodProcessorTest.kt
M       room/compiler/src/test/kotlin/androidx/room/testing/TestProcessor.kt

https://android-review.googlesource.com/1123258
https://goto.google.com/android-sha1/b90079595f33f58fece04026a97faa0d243acdb1

  The following changes were cherrypicked through Coastguard (https://android-build.googleplex.com/coastguard/)
  Release Track: (https://android-build.googleplex.com/coastguard/dashboard/6093116828680192/#/cherrypickHistory/all)
  Created: 2019-10-14 17:23:42.610596+00:00
  Changes: aosp/1123258
 

Project: platform/frameworks/support
Branch: androidx-master-dev

commit bdde5a1a970ddc9007b28de4aa29d60ffa588f08
Author: Yigit Boyar <yboyar@google.com>
Date:   Thu Apr 16 16:47:05 2020

    Re-factor how errors are dismissed when query is re-written
   
    This CL changes how we handle errors/warnings if query is
    re-written.
    There was a bug in expandProjection where we would report warnings
    for things that Room already fixes automatically (b/140759491).
    The solution to that problem (I7659002e5e0d1ef60fc1af2a625c0c36da0664d8)
    solved it by deferring validating of columns until after re-write
    decision is made. Unfortunately, this required changing PojoRowAdapter
    to have a dummy mapping until it is validating, make it hard to use
    as it does have a non-null mapping which is not useful.
   
    This CL partially reverts that change and instead rely on the log
    deferring logic we have in Context. This way, we don't need to break
    the stability of PojoRowAdapter while still having the ability to
    drop warnings that room fixes. This will also play nicer when we
    have different query re-writing options that can use more information
    about the query results.
   
    Bug: 153387066
    Bug: 140759491
    Test: existing tests pass
    Change-Id: I2ec967c763d33d7a3ff02c1a13c6953b460d1e5f

M       room/compiler/src/main/kotlin/androidx/room/log/RLog.kt
M       room/compiler/src/main/kotlin/androidx/room/processor/QueryMethodProcessor.kt
M       room/compiler/src/main/kotlin/androidx/room/solver/TypeAdapterStore.kt
M       room/compiler/src/main/kotlin/androidx/room/solver/query/result/PojoRowAdapter.kt

https://android-review.googlesource.com/1288456

#3: This is exactly what an internal implementation would look like because the backing JobScheduler does not support initial delays on periodic work.  I realize that WorkManager doing it for you is nicer, which is why this feature request is still open, but it may take us some time to get to it.

#4: Please file a separate bug if that doesn't work for you.

#5: How could I debug the behaviour of this chain of Work?

Use logcat, or use the various getStatus methods to see what's going on.  File a bug with a bugreport and sample code that results in the problem.

It would be nice to see setInitialDelay() on PeriodicWorkRequest.Builder in the next version, Thanks

Just a "+1" "me too" to add another voice to this... would make so much sense to be able to have setInitialDelay() on PeriodicWorkRequest.Builder

Android must list down the challenges of Periodic Work request  in there documents, I am  tracking Work Manager since it was alpha.Here are the limitations of Priodic Work request:
1. Periodic work request does not support setInitialDelay.
2. Periodic Work request does not support the Chining.

Both of these items are listed in the official documentation for PeriodicWorkRequest: https://developer.android.com/reference/androidx/work/PeriodicWorkRequest

"Periodic work has a minimum interval of 15 minutes and it cannot have an initial delay."
"Periodic work cannot be part of a chain or graph of work."

Still not supported...
I feel that many people need it...would make so much sense to be able to have setInitialDelay() on PeriodicWorkRequest.Builder

Setting a flex period effectively delays a PeriodicWorkRequest.

+1 from me too, with an extra option to limit the number of repeats, for example, run a periodic job daily for 7 days and then stop.

+1 for setInitailDelay() and limitNumberOfFires() for Periodic work request!

What is the best solution for now to setInitailDelay() ?

You can use a PeriodicWorkRequest.Builder with a flex Period as suggested in #13.
This behaviour is documented: https://developer.android.com/reference/androidx/work/PeriodicWorkRequest.Builder#PeriodicWorkRequest.Builder(java.lang.Class%3C?%20extends%20androidx.work.ListenableWorker%3E,%20long,%20java.util.concurrent.TimeUnit,%20long,%20java.util.concurrent.TimeUnit)

The call creates a PeriodicWorkRequest to run periodically once within the flex period of every interval period.

What I mean by setInitailDelay() is the delay before the first run then a fixed periodic delay.

Project: platform/frameworks/support
Branch: androidx-master-dev

commit 25dc21990f5b0d606f3141b9120516b880599b6c
Author: Rahul Ravikumar <rahulrav@google.com>
Date:   Mon Apr 29 10:27:18 2019

    Add support for initialDelays for PeriodicWorkRequests.
   
    Test: Additional WorkSpecTest unit tests.
    Integration tests on API 23, and API 21.
   
    Fixes: b/111404867
   
    Change-Id: I9eae1c7cf527c231b831f22c6a2d10089d6a63c9

M       work/integration-tests/testapp/src/main/java/androidx/work/integration/testapp/MainActivity.java
M       work/integration-tests/testapp/src/main/res/layout/activity_main.xml
M       work/integration-tests/testapp/src/main/res/values/strings.xml
M       work/workmanager/api/2.1.0-alpha01.txt
M       work/workmanager/api/current.txt
M       work/workmanager/src/androidTest/java/androidx/work/WorkSpecTest.java
M       work/workmanager/src/main/java/androidx/work/OneTimeWorkRequest.java
M       work/workmanager/src/main/java/androidx/work/WorkRequest.java
M       work/workmanager/src/main/java/androidx/work/impl/WorkerWrapper.java
M       work/workmanager/src/main/java/androidx/work/impl/background/systemjob/SystemJobScheduler.java
M       work/workmanager/src/main/java/androidx/work/impl/model/WorkSpec.java

https://android-review.googlesource.com/953484
https://goto.google.com/android-sha1/25dc21990f5b0d606f3141b9120516b880599b6c

still can't rely on it :(
I calculate millis to midnight and schedule a daily backup with PeriodicWorkRequest (should happen each 24h), and it just won't fire up the Worker.
When I remove setInitialDelay() call, PeriodicWorkRequest - it works!

classic