Joffrey Bion

Hi, thanks a lot for the report! At first glance, 2 things catch my attention: 1. the `host` is set to `/` in the `client.connect(...)` call, why is that? `/`...

Thanks for the extra information. I'll make the connection resistant to weird heart beats, but it might not fix your root issue. Maybe the initial connection/session is not closed (despite...

Yep I'm aware of how `lifecycleScope` behaves, but since cancellation is cooperative, there is no real guarantee that the coroutine will be completed and the session closed. Technically we know...

@EslamMohamed3396 did you get the chance to understand how you're getting heartbeats there from a previous connection? I was thinking that even if I add a feature/config to ignore such...

Based on the details above, here is what I think we should do. * Commands with 0 parameters: * No input class, no builder * Command method with no arguments...

> This is a perfect example: https://github.com/Kotlin/kotlinx.coroutines/issues/1814#issuecomment-588317835. Why isn't it more considered ? @NinoDLC It's not an example *use case*, it's a made-up experiment to demonstrate a behaviour. The `runCatching`...

> To me, it's an anti-pattern for a coroutine to be able to prevent the termination of its scope @NinoDLC coroutine cancellation is cooperative, so in the general case there...

> "runTest" is such a generic name it implies that it is just "the way to do tests", StandardTestDispatcher implies this even stronger. With such a generic name I would...

> So, the name is chosen based on which one addresses the needs of the average test the best. I guess that's where opinions diverge. Skipping delays doesn't seem to...

> In general, this issue is getting way less attention than the other ones Fair enough. > With an audience as extensive as ours, doing anything unanimously is impossible. My...