You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I'm using the transaction API but it seems the transaction always gets stuck after executing the first step.
I'm using EdgeDB 5.6 on EdgeDB Cloud and Java client library version 0.3.0.
Here is a simple example using Kotlin.
packagecom.test.edgedbclientimportcom.edgedb.driver.EdgeDBClientimportcom.edgedb.driver.EdgeDBConnectionimportkotlinx.coroutines.future.awaitsuspendfunmain() {
val client =EdgeDBClient(EdgeDBConnection.parse(null, null, true))
val output = client.transaction { tx ->
tx.query(String::class.java, "SELECT 'Hello, World 1!'")
.thenCompose {
println("Output0: $it")
tx.query(String::class.java, "SELECT 'Hello, World 2!'")
}
.thenCompose {
println("Output1: $it")
tx.query(String::class.java, "SELECT 'Hello, World 3!'")
}
}.await()
println("--- Completed ---")
println("Final output: $output")
client.close()
}
The output is Output0: [Hello, World 1!] from the first step and then it's stuck.
I believe this is happening due to the semaphore in TransactionImpl being acquired
Hi,
I'm using the transaction API but it seems the transaction always gets stuck after executing the first step.
I'm using EdgeDB 5.6 on EdgeDB Cloud and Java client library version 0.3.0.
Here is a simple example using Kotlin.
The output is
Output0: [Hello, World 1!]
from the first step and then it's stuck.I believe this is happening due to the semaphore in
TransactionImpl
being acquirededgedb-java/src/driver/src/main/java/com/edgedb/driver/internal/TransactionImpl.java
Lines 98 to 114 in 3ddbee1
but never being released in the
executeTransactionStep
method after completion of the step.edgedb-java/src/driver/src/main/java/com/edgedb/driver/internal/TransactionImpl.java
Lines 71 to 96 in 3ddbee1
This issue could be the same as #21.
Please let me know if any other details are required.
Thanks
The text was updated successfully, but these errors were encountered: