The collector starts undispatched to catch synchronous emissions

I can remove the

undispatched

one, as I said, my problem is the

Unconfined

context

, and I really don't know if it is useful. Do you think

context

fits in

test

function?

suspend fun <T> Flow<T>.test(
  timeout: Duration = 1.seconds,
  context: CoroutineContext = Unconfined,
  validate: suspend FlowTurbine<T>.() -> Unit
) {
  coroutineScope {
  ...

    val collectJob = launch(start = UNDISPATCHED, context = context) {
      ...
    }
  }
}

It's unconfined so that it runs synchronously on emission and schedules the suspended expect to wake back up

is the okio 3 alpha binary compatible with 2.x?

whats the appropriate way to execute a sqldelight query in a suspend fun? doesn't look like the generated class exposes any suspending functions

withContext(IO) { stuff.execute() }

is there any updated guidance on inserting multiple rows at once with SQLDelight? i've only come across https://github.com/cashapp/sqldelight/issues/548 but the code its using seems out of date

Insert one by one in a transaction

I wish it was possible to call suspend functions from within a transaction :(

That would lock the database as read only for an indeterminate amount of time

Would that be a realistic problem though? AndroidX provides an inline transaction function which allows for this: https://developer.android.com/reference/kotlin/androidx/sqlite/db/package-summary#(androidx.sqlite.db.SupportSQLi[…]lin.Boolean,%20kotlin.Function1)

They're forced to because otherwise you couldn't use your suspend-based DAO methods. Since SQLDelight always exposes the ability to execute synchronously we don't have that problem. Also have you looked at the insane hacks that they do in order to support this?

Ok, fair enough. My issue is that I’m implementing a large bulk insert, but the inserts are not simple. I need to do several queries for each one, on the fly, and the nature of the queries varies too. I already have exposed suspend funs for those queries but cannot use them. Is it a sign that I shouldn’t have exposed those as suspend funs in the first place? Keep them blocking instead and just use

withContext(<http://Dispatchers.IO|Dispatchers.IO>)

further up the call hierarchy?

@Mark if they're called from outside the class and also used inside other functions in the class you can make a them non suspending and private then make a public suspending function that just calls the private non suspending one, that's what i'm trying out for now

What happens if transactions are "nested" e.g functions A and B which both use transactions are called by function C which uses them inside a transaction, are they still all 2/3 separate transactions?

nested transaction behavior is dictated by the underlying database. for sqlite, you can read about it here: https://sqlite.org/lang_savepoint.html

Anvil

2.0.14

still doesn't work with kotlin

1.4.30

e: java.lang.NoSuchMethodError: 'void org.jetbrains.kotlin.analyzer.AnalysisResult$RetryWithAdditionalRoots.<init>(org.jetbrains.kotlin.resolve.BindingContext, org.jetbrains.kotlin.descriptors.ModuleDescriptor, java.util.List, java.util.List, boolean)'
        at com.squareup.anvil.compiler.codegen.CodeGenerationExtension.analysisCompleted(CodeGenerationExtension.kt:81)
        at org.jetbrains.kotlin.cli.jvm.compiler.TopDownAnalyzerFacadeForJVM.analyzeFilesWithJavaIntegration$invokeExtensionsOnAnalysisComplete(TopDownAnalyzerFacadeForJVM.kt:108)
        at org.jetbrains.kotlin.cli.jvm.compiler.TopDownAnalyzerFacadeForJVM.analyzeFilesWithJavaIntegration(TopDownAnalyzerFacadeForJVM.kt:118)
        at org.jetbrains.kotlin.cli.jvm.compiler.TopDownAnalyzerFacadeForJVM.analyzeFilesWithJavaIntegration$default(TopDownAnalyzerFacadeForJVM.kt:85)

I ran this with

--rerun-tasks

so I assume its no wrong cache or something like that

Sample project: https://github.com/PaulWoitaschek/AnvilBug

./gradlew app:assembleDebug

File a bug?

Cc @ralf

Support for 1.4.30 just merged, and while the change log says there were two releases yesterday, neither of them mention it. https://github.com/square/anvil/pull/193

I'll push a release later today.

I added the details and a repro to the closed issue

Apparently it just wasn't released yet

The rare sqldelight updates are holding us back. Is it possible to release versions with the latest kotlin version more frequently? Id like to update to 1.4.30 but can't due to binary incompatibilities between kotlin native versions

Has SQLiter done an update

We’re usually waiting on that but I haven’t been keeping up to date

Also coroutines native-mt needs a release presumably

Lots of upstream deps. If you ever notice they're all upgraded you can send a PR to bump things