this is full stack trace.

# coroutines

[tateisu]

this is full stack trace.

-.scala

[gildor]

This is because of coroutineScope

[tateisu]

I believe launch{} requires something kind of CoroutineScope, but other type of scope builder raises same result. how to fix it?

[gildor]

Exactly, you just all the time tries to hide you async code

[gildor]

you shouldn’t do this

[gildor]

and use parent coroutine scope instead

[gildor]

I don’t know what exactly you want to achive, as I said, so hard to give you advice

[tateisu]

I would like to see the smallest example that uses CoroutineExceptionHandler. Is that deprecated?

[gildor]

No, it is not

[gildor]

just do not use coroutineScope function which has different semantics

[gildor]

use GlobalScope or some parent scope for those examples

[tateisu]

Ok, this worked. thanks.

GlobalScope.launch( handler)  {
        error("inside launch")
    }
    delay(1000)

[tateisu]

CoroutineExceptionHandler can't cooperative with structured concurrency?

[gildor]

Also instead you can make your test coroutines exception handler function extension to coroutine scope, this is how this should work in real life rather than use GlobalScope

[gildor]

But it's of course fine just if you want to play with some function

[gildor]

CoroutineExceptionHandler can't cooperative with structured concurrency?

It can, but you should use supervision scope otherwise parent will be cancelled in case of error

[tateisu]

now I checked SupervisorCoroutine's code and I see it have override fun childCancelled(cause: Throwable): Boolean = false . this is reason why it is not help that just using outer context + SupervisorJob . thanks.