Infeasible
Status Update
Comments
jo...@google.com <jo...@google.com> #2
Project: platform/frameworks/support
Branch: androidx-main
Author: Daniel Santiago Rivera <
Link:
Use Context.getDatabasePath() when a driver is configured.
Expand for full commit details
Use Context.getDatabasePath() when a driver is configured.
This helps users migrating to driver APIs that use simple database names and expect Room to figure out the directory to store the database, for which the SupportSQLiteOpenHelper is responsible off when no driver is used.
Since getDatabasePath() does some IO, a hook for the driver wrapper in the base connection manager was added so that the file name could be resolved, lazily and in the background thread where the connection is being opened.
Lastly, if a bad path is used, a more proper error will be thrown instead of an obscure 'can't create file lock' since creating a file lock will first be attempted before actually creating / opening the actual database.
Bug: 377830104
Test: BuilderTest
Change-Id: I833154e2855a38520e5a0e8c802964bd455000e8
Files:
- M
room/integration-tests/multiplatformtestapp/src/androidInstrumentedTest/kotlin/androidx/room/integration/multiplatformtestapp/test/BuilderTest.kt
- M
room/room-runtime/src/androidMain/kotlin/androidx/room/RoomConnectionManager.android.kt
- M
room/room-runtime/src/commonMain/kotlin/androidx/room/RoomConnectionManager.kt
- M
room/room-runtime/src/commonMain/kotlin/androidx/room/concurrent/ExclusiveLock.kt
Hash: 35ddf21c6ede1af577d2d20b96107e04988b04e0
Date: Fri Jan 17 15:42:06 2025
ha...@gmail.com <ha...@gmail.com> #3
The following release(s) address this bug.It is possible this bug has only been partially addressed:
androidx.room:room-runtime:2.7.0-alpha13
androidx.room:room-runtime-android:2.7.0-alpha13
androidx.room:room-runtime-iosarm64:2.7.0-alpha13
androidx.room:room-runtime-iossimulatorarm64:2.7.0-alpha13
androidx.room:room-runtime-iosx64:2.7.0-alpha13
androidx.room:room-runtime-jvm:2.7.0-alpha13
androidx.room:room-runtime-linuxarm64:2.7.0-alpha13
androidx.room:room-runtime-linuxx64:2.7.0-alpha13
androidx.room:room-runtime-macosarm64:2.7.0-alpha13
androidx.room:room-runtime-macosx64:2.7.0-alpha13
Description
This is about the Atom feeds for YouTube channels, for example:https://www.youtube.com/feeds/videos.xml?channel_id=UC_iD0xppBwwsrM9DegC5cQQ
The feeds specify the
id
as follows:<id>yt:channel:</id>
. Note that there is no channel id inside the id, in contrast to episodes where there is an id:<id>yt:video:RFm3CSkoPGQ</id>
. Therefore, all YouTube Atom feeds specify the same id.According to the specifications, Atom ids:
The idea of the tag is that applications can detect duplicate Atom feeds and possibly merge them. Because all YouTube feeds now have the same id, a standards-compliant feed reader detects all YouTube feeds as the same feed (possibly collapsing them into one feed).
Note that this is a new problem. The ids were available a few months ago. To me, it looks like some variable placement in the template of the YouTube Atom feed is broken.