A modern programming language that makes developers happier.

kotlinlang

Any suggestions how to fix below which happened under server CIO load test:
```io.ktor.server.cio.HttpServer Fatal exception in coroutines machinery for DispatchedContinuation[ExperimentalCoroutineDispatcher@4bf56b31[scheduler = DefaultDispatcher@1571ced[Pool Size {core = 2, max = 128}, Worker States {CPU = 2, blocking = 1, parked = 0, retired = 0, terminated = 0}, running workers queues = [2c, 0b, 0c], global queue size = 0, Control State Workers {created = 3, blocking = 1}]], Continuation at io.ktor.http.cio.PipelineKt$startConnectionPipeline$1$outputsActor$1.invokeSuspend(Pipeline.kt:77)@7b0cac71]. Please read KDoc to 'handleFatalException' method and report this incident to maintainers```


Could you please post the whole stacktrace?

Jul 13 19:20:12.632 | staging-65599dc5d6-44wnw | 2020-07-13 16:20:12.632 [DefaultDispatcher-worker-3] ERROR io.ktor.server.cio.HttpServer Fatal exception in coroutines machinery for DispatchedContinuation[ExperimentalCoroutineDispatcher@4bf56b31[scheduler = DefaultDispatcher@1571ced[Pool Size {core = 2, max = 128}, Worker States {CPU = 1, blocking = 1, parked = 1, retired = 0, terminated = 0}, running workers queues = [0b, 0c], global queue size = 0, Control State Workers {created = 3, blocking = 1}]], Continuation at io.ktor.http.cio.PipelineKt$startConnectionPipeline$1$outputsActor$1.invokeSuspend(Pipeline.kt:77)@589a6263]. Please read KDoc to 'handleFatalException' method and report this incident to maintainers
Jul 13 19:20:12.632 | staging-65599dc5d6-44wnw | kotlinx.coroutines.CoroutinesInternalError: Fatal exception in coroutines machinery for DispatchedContinuation[ExperimentalCoroutineDispatcher@4bf56b31[scheduler = DefaultDispatcher@1571ced[Pool Size {core = 2, max = 128}, Worker States {CPU = 1, blocking = 1, parked = 1, retired = 0, terminated = 0}, running workers queues = [0b, 0c], global queue size = 0, Control State Workers {created = 3, blocking = 1}]], Continuation at io.ktor.http.cio.PipelineKt$startConnectionPipeline$1$outputsActor$1.invokeSuspend(Pipeline.kt:77)@589a6263]. Please read KDoc to 'handleFatalException' method and report this incident to maintainers
Jul 13 19:20:12.633 | staging-65599dc5d6-44wnw | 	at kotlinx.coroutines.DispatchedTask.handleFatalException$kotlinx_coroutines_core(Dispatched.kt:278)
Jul 13 19:20:12.633 | staging-65599dc5d6-44wnw | 	at kotlinx.coroutines.DispatchedTask.run(Dispatched.kt:249)
Jul 13 19:20:12.633 | staging-65599dc5d6-44wnw | 	at kotlinx.coroutines.scheduling.CoroutineScheduler.runSafely(CoroutineScheduler.kt:594)
Jul 13 19:20:12.633 | staging-65599dc5d6-44wnw | 	at kotlinx.coroutines.scheduling.CoroutineScheduler.access$runSafely(CoroutineScheduler.kt:60)
Jul 13 19:20:12.633 | staging-65599dc5d6-44wnw | 	at kotlinx.coroutines.scheduling.CoroutineScheduler$Worker.run(CoroutineScheduler.kt:740)
Jul 13 19:20:12.633 | staging-65599dc5d6-44wnw | Caused by: java.lang.IllegalStateException: Job ActorCoroutine{Cancelled}@279f869e is already complete or completing, but is being completed with kotlin.Unit
Jul 13 19:20:12.633 | staging-65599dc5d6-44wnw | 	at kotlinx.coroutines.JobSupport.makeCompletingOnce$kotlinx_coroutines_core(JobSupport.kt:788)
Jul 13 19:20:12.633 | staging-65599dc5d6-44wnw | 	at kotlinx.coroutines.AbstractCoroutine.resumeWith(AbstractCoroutine.kt:111)
Jul 13 19:20:12.633 | staging-65599dc5d6-44wnw | 	at kotlin.coroutines.jvm.internal.BaseContinuationImpl.resumeWith(ContinuationImpl.kt:46)
Jul 13 19:20:12.633 | staging-65599dc5d6-44wnw | 	at kotlinx.coroutines.DispatchedTask.run(Dispatched.kt:334)
Jul 13 19:20:12.633 | staging-65599dc5d6-44wnw | 	... 3 common frames omitted