It seems that adding `yield()`s in between and a `delay(1000L)` helps... not sure what the problems ...

# coroutines

[dave08]

It seems that adding `yield()`s in between and a delay(1000L) helps... not sure what the problems was though... 🤔.

[Sinan Kozak]

It is probably that they collect in same scope.

[dave08]

But it launches a coroutine for each (launchIn(scope))

[Sinan Kozak]

Or your test finishes before all onEach gets called

[Sinan Kozak]

Let me try on ide

[dave08]

That's covered by the delay, but doesn't explain the yeild

[dave08]

yield

[Sinan Kozak]

it is not about delay. yield is enough. And probably reason is runBlocking’s scope finishes before first onEach find time to execute

[Sinan Kozak]

runBlocking {
  println("start")

  val job1 = state
      .onEach { println("$it-1") }
      .launchIn(scope)
  println("here")

  state.value = 2
  val job2 = state
      .onEach { println("$it-2") }
      .launchIn(scope)

  state.value = 3
  println("finished")

  job1.cancelAndJoin()
  job2.cancelAndJoin()
}

[Sinan Kozak]

You need to cancel your jobs of launchIns. otherwise runBlockings scope finishes and script finish without checking val scopes state.

[Sinan Kozak]

you can also just cancel the val scope at the end of runBlocking

[Sinan Kozak]

scope.cancel()

[dave08]

Thanks! With scope.cancel() I got completely different results..

[Sinan Kozak]

It is a race condition and leak of scope. scope continue running when runblocking finishes but when runblocking finishes all script finishes 😅

[dave08]

Thanks for the explanation 😊!