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

Project: platform/frameworks/support
Branch: androidx-main

commit ff398f939baaa4e6fec4eaefbe2b27767c056028
Author: Ian Baker <ibaker@google.com>
Date:   Thu Feb 23 14:43:05 2023

    Add test for invalid IFD offset in ExifInterface
   
    jpeg_with_exif_invalid_offset.jpg was created by modifying the offset
    of the ExifIFD from 0x00000008 to 0x00abcd08 (i.e. well outside the
    exif block of the jpeg file).
   
    The current behaviour of ExifInterface stops parsing the file
    completely at this point, and thus never parses the `GpsInfo` (which
    is the next tag after the ExifIFD pointer). An upcoming change will
    make ExifInterface skip the invalid offset, but continue parsing later
    tags, and therefore the GPS info will be successfully parsed from this
    broken file.
   
    Broken/invalid IFD offsets are noted to be a common failure mode in exif
    data (see top bullet of https://en.wikipedia.org/wiki/Exif#Technical_2).
   
    exiftool complains about the invalid offset but is able to parse the
    GPS data:
   
    $ exiftool -v4 jpeg_with_exif_invalid_offset.jpg
      <snip>
      | 6)  ExifOffset (SubDirectory) -->
      |     - Tag 0x8769 (4 bytes, int32u[1]):
      |         01e6: 00 ab cd 08                                     [....]
      | Warning = Bad ExifOffset SubDirectory start (directory end is 11259148 but EXIF size is only 790)
      | 7)  GPSInfo (SubDirectory) -->
      |     - Tag 0x8825 (4 bytes, int32u[1]):
      |         01f2: 00 00 01 16                                     [....]
      | + [GPS directory with 9 entries]
      | | 0)  GPSLatitudeRef = N
      | |     - Tag 0x0001 (2 bytes, string[2]):
      | |         012c: 4e 00                                           [N.]
      <snip>
   
    Test: ./gradlew :exifinterface:exifinterface:connectedAndroidTest
    Bug: 264729367
    Change-Id: I1782d5bef9d91caa2fd97508bdf6c3924a7d7963

M       exifinterface/exifinterface/src/androidTest/java/androidx/exifinterface/media/ExifInterfaceTest.java
A       exifinterface/exifinterface/src/androidTest/res/raw/jpeg_with_exif_invalid_offset.jpg
M       exifinterface/exifinterface/src/androidTest/res/values/arrays.xml

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