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

I will mark is as blocked by b/154920561 as we first need to make the following fix, and when this case is fixed I can recommend how to avoid clashes with the better messaging

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

commit 5ec2ca9d0adff00297ca0a42a69307aa14341e80
Author: Andrey Kulikov <andreykulikov@google.com>
Date:   Fri Jul 31 17:40:46 2020

    Allow having multiple value providers for the same savedInstanceState() key
   
    Originally we were hoping to solve the unique keys issue fully on a compose compiler/runtime side, but it is not trivial and will make the runtime way less efficient still without 100 percent uniqueness guarantees.
   
    The simple case which is not currently working is
    list.forEach {
       savedInstanceState { 0 }
    }
    Runtime keys are the keys generated during the compilation for the hash of the function invocation location in the codebase. In the for loop we have two invocations with the same key and we can't do anything more clever than just allow multiple invocations with the same key and use the order in which they are executed to differentiate them. Which makes this code basically equivalent to
    list.forEachIndexed { index, item ->
       key(index) {
           savedInstanceState { 0 }
       }
    }
    But still allows to provide more reasonable keys if the user needs it
    list.forEach { item ->
       key(item.myUniqueKey) {
           savedInstanceState { 0 }
       }
    }
    To allow state to be "moved" together with the item if the items in a list was reordered.
   
    Given that we have to adjust how UiSavedStateRegistry works and replicate the runtime behavior. There are could be multiple providers registered for the same [key]. In this case the order in which they were registered matters.
   
    Say we registered two providers for the key. One provides "1", second provides "2".
    [performSave] in this case will have listOf("1", "2) as a value for the key in the map. And later, when the registry will be recreated with the previously saved values, the first execution of [consumeRestored] would consume "1" and the second one "2".
   
    In addition to this change I also refactored rememberSavedInstanceState() implementation to be more prepared for future possible cases when the compose transaction can fail (we can only save the values during composition in state objects) and should use onCommit like behaviour for registering/unregistering the providers.
    Also in light of deprecation of state { } composable in favour to remember { mutableStateOf() } I decided to add a more meaningful error message if the user will try to write rememberSavedInstanceState { mutableStateOf() } to guide people to use savedInstanceState() which provides a Saver implementation for MutableState
   
    Fixes: 160042650
    Fixes: 156853976
    Fixes: 159026663
    Fixes: 154920561
    Relnote: Crash when something which saves the state was used inside the for loop is fixed. Now having the same key in savedInstanceState() is allowed, api of UiSavedStateRegistry is now adjusted to this new requirement
    Test: new tests, manually
    Change-Id: I4ab7630120ffce145d1bf09d52a475d197030150

M       ui/ui-core/src/androidMain/kotlin/androidx/compose/ui/platform/DisposableUiSavedStateRegistry.kt
M       ui/ui-saved-instance-state/api/current.txt
M       ui/ui-saved-instance-state/api/public_plus_experimental_current.txt
M       ui/ui-saved-instance-state/api/restricted_current.txt
M       ui/ui-saved-instance-state/src/androidAndroidTest/kotlin/androidx/compose/runtime/savedinstancestate/RememberSavedInstanceStateTest.kt
A       ui/ui-saved-instance-state/src/androidAndroidTest/kotlin/androidx/compose/runtime/savedinstancestate/RestorationInVariousScenariosTest.kt
M       ui/ui-saved-instance-state/src/commonMain/kotlin/androidx/compose/runtime/savedinstancestate/RememberSavedInstanceState.kt
M       ui/ui-saved-instance-state/src/commonMain/kotlin/androidx/compose/runtime/savedinstancestate/Saver.kt
M       ui/ui-saved-instance-state/src/commonMain/kotlin/androidx/compose/runtime/savedinstancestate/UiSavedStateRegistry.kt
M       ui/ui-saved-instance-state/src/test/java/androidx/compose/runtime/savedinstancestate/AutoSaverTest.kt
M       ui/ui-saved-instance-state/src/test/java/androidx/compose/runtime/savedinstancestate/UiSavedStateRegistryTest.kt
M       ui/ui-test/src/androidMain/kotlin/androidx/ui/test/StateRestorationTester.kt

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