Infeasible
Status Update
No update yet.
Comments
po...@gmail.com
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
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
po...@gmail.com
ch...@google.com
rk...@google.com
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 (
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
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 (
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
po...@gmail.com
it was already reported it to apple. just opened an issue there, in case.
thanks tho.
thanks tho.
rk...@google.com
Thank you for reporting this to Apple and letting us know.
po...@gmail.com
Hey guys, just so you know, MacOS 15.4 Beta 2 dropped out today, and it fixed the bug.
rk...@google.com
ᐠ(ᐛ)ᐟ
jp...@google.com
Indeed !
It's even in their release notes:
Upon update to macOS 15.4 beta 1, M4 Macs will be unable to launch virtual machines and attempts will result in a system restart. (145309647) (FB16542958)
po...@gmail.com
well, fun fact, i was still able to run debian and even windows virtual machines on my mac.
but anyway, it's fixed now. have a great day guys!
but anyway, it's fixed now. have a great day guys!
Description
####################################################
Please provide all of the following information, otherwise we may not be able to route your bug report.
####################################################
1. Describe the bug or issue that you're seeing.
Hi. First of all, I know the risks of running a Dev Beta -> that's why I'm making a report.
MacOS (15.4 - Dev Beta 1 - 24E5206s) on a MacBook Pro M4 Pro crashes (Kernel Panic) exclusively when starting the Emulator.
According to ChatGPT (after giving it the crash logs generated by MacOS, not the files from AndroidStudio), the issue seems to be related to TailspinSymbolicationServer, which crashes due to a segmentation fault (EXC_BAD_ACCESS (SIGSEGV)). The logs indicate a KERN_INVALID_ADDRESS error at 0x0000000000001010. Additionally, fsck and diskutil checks show no filesystem corruption, meaning the issue does not appear to be related to disk integrity.
The problem occurs only when launching the Android Emulator—other system functions and applications run without any noticeable issues. However, the crash forces a full system reboot, making it impossible to use the emulator on this setup.
2. Attach log files from Android Studio
2A. In the IDE, select the Help..Collect Logs and Diagnostic Data menu option.
2B. Create a diagnostic report and save it to your local computer.
2C. Attach the report to this bug using the Add attachments button.
3. If you know what they are, write the steps to reproduce:
3A. Start any Android Emulator -- different versions tried, different devices also.
In addition to logs, please attach a screenshot or recording that illustrates the problem.
Can't really do this since the computer crashes. Just imagine it a starting the emulator by any way (play icon at top-right, + icon on the emulator window itself...) and completely freezing then rebooting on itself after 10-20s. Everything is unresponsive (trackpad, buttons...)
For more information on how to get your bug routed quickly, see
Build: AI-242.23726.103.2422.13103373, 202502212014
AS: Ladybug Feature Drop | 2024.2.2 Patch 2
AI-242.23726.103.2422.13103373, JRE 21.0.5+-13047016-b750.29x64 JetBrains s.r.o., OS Mac OS X(aarch64) v15.4, screens 3600x2338 (200%), 1920x1080 (100%); Retina
Android Gradle Plugin: 8.8.2
Gradle: 8.10.2
Gradle JDK: JetBrains Runtime 21.0.5 - aarch64
NDK: from local.properties: (not specified), latest from SDK: (not found)
CMake: from local.properties: (not specified), latest from SDK: (not found), from PATH: (not found)
```