I am using `runBlocking(someContext)`, and within the block a call is made to a method that is calli...

# coroutines

[Kris Wong]

I am using runBlocking(someContext), and within the block a call is made to a method that is calling launch using a scope that was created with the same context. however, it is not blocking. am I doing something wrong?

[octylFractal]

could you share the code in full, or at least condensed? that sounds correct but maybe there's a miscommunication

[streetsofboston]

Structured Concurrency only works within one scope. If a launch is launched with a different scope, it will not participate in the structured concurrency of the calling scope.

It looks like sharing a CoroutineContext does not circumvent this...

[Kris Wong]

runBlocking(anObject.coroutineContext) {
    anObject.doSomething()
}

and

fun doSomething() {
    coroutineScope.launch {
        ...
    }
}

finally

internal val coroutineContext = Executors.newSingleThreadExecutor().asCoroutineDispatcher()
private val coroutineScope = CoroutineScope(coroutineContext + SupervisorJob())

[Kris Wong]

a scope just contains a context, so my understanding was that this is the way to accomplish what I am after

[octylFractal]

no, this will not work because doSomething is not using a child job of runBlocking

[octylFractal]

you should pass down the scope given in the runBlocking lambda, and use that to launch the appropriate job, OR if you mean to make it separate, return the Job from doSomething() and join() on it in runBlocking

[Kris Wong]

hmm

[Kris Wong]

i am just trying to test something that is otherwise fully encapsulated, in the least invasive way

[Kris Wong]

testing classes with no output always ends up being a pain =/

[Kris Wong]

alright, at least I understand the problem, thanks!