Concurrency runInTransaction cause InterruptedException [400584611]

Fixed

Bug

Status Update

No update yet.

Description

ly...@gmail.com

created issue #1

Mar 4, 2025 09:48AM

Component used:room

Version used:2.7.0-rc01

Exception

    Caused by: java.lang.InterruptedException
    	at kotlinx.coroutines.BlockingCoroutine.joinBlocking(Builders.kt:94)
    	at kotlinx.coroutines.BuildersKt__BuildersKt.runBlocking(Builders.kt:69)
    	at kotlinx.coroutines.BuildersKt.runBlocking(Unknown Source:1)
    	at kotlinx.coroutines.BuildersKt__BuildersKt.runBlocking$default(Builders.kt:47)
    	at kotlinx.coroutines.BuildersKt.runBlocking$default(Unknown Source:1)
    	at androidx.room.util.DBUtil__DBUtil_androidKt.performBlocking(DBUtil.android.kt:69)
    	at androidx.room.util.DBUtil.performBlocking(Unknown Source:1)
    	at XXXDao_Impl.xxxxx(XXXDao_Impl.kt)
    	at androidx.room.RoomDatabase.runInTransaction(RoomDatabase.android.kt:733)

PS, please don't reference my email in comment

Comments

ly...@gmail.com <ly...@gmail.com> #2Mar 5, 2025 01:39AM

+1 to this feature request, came here seeking help at

https://serverfault.com/questions/987908/custom-routes-rejected-by-gke-peer-configuration/988167#988167
We will to build CD pipelines with agents running in internal on-premise network, peered with GCP network. GKE private endpoint is not reachable in this case.

da...@google.com <da...@google.com> #3Mar 6, 2025 02:41PM

+1 Could be quite a useful feature for us.
Ideally, we don't want to have public IP for K8S API at all and manage it privately inside the org with a hybrid architecture site-2-site VPN etc.

ly...@gmail.com <ly...@gmail.com> #4Mar 7, 2025 12:15AM

I thought this would be resolved now that the VPC Peerings of private GKE will accept routes exported from the VPC. But it still doesn't seem to work for me.

ly...@gmail.com <ly...@gmail.com> #5Mar 11, 2025 06:24AM

Same issue. According to

https://cloud.google.com/kubernetes-engine/docs/how-to/private-clusters#master-on-prem-routing it should work, but still KO for me

da...@google.com <da...@google.com> #6Mar 13, 2025 12:39PM

Does anyone has been able to make it works?

ap...@google.com <ap...@google.com> #7Mar 19, 2025 03:19PM

I stumbled upon this issue and wanted to share some thoughts on how we fixed this. Following the documentation listed above, there is a reference to the VPC peering connection, which links here:

https://cloud.google.com/vpc/docs/using-vpc-peering#update-peer-connection. After setting the "Export custom routes" bit, I was able to start connecting from my private network. The exported routes bit injects the static/dynamic routes to the peered VPC, which therefore allows responses to flow backward to the clients from the api server.

ap...@google.com <ap...@google.com> #8Mar 19, 2025 10:17PM

da...@myfitnesspal.com. - this does not work with private ip , something else in your setup (like public ip, nat or something) made it work, not the export/import , this issue was verified by google support investigating all setups in our projects including export/import custom routes.

da...@google.com <da...@google.com> Mar 19, 2025 10:18PM

Marked as fixed.