Hello. I’m recieving this and it’s error message i...

# arrow

[Kev]

Hello. I’m recieving this and it’s error message is to let you guys know.

Exception in thread "DefaultDispatcher-worker-3" kotlinx.coroutines.CoroutinesInternalError: Fatal exception in coroutines machinery for CancellableContinuation(DispatchedContinuation[Dispatchers.Unconfined, Continuation at arrow.fx.coroutines.ParMapKt$parMapOrAccumulate$6.invokeSuspend(ParMap.kt:106)@1a242fa7]){Completed}@3dd08fb3. Please read KDoc to 'handleFatalException' method and report this incident to maintainers

Any ideas?

[Youssef Shoaib [MOD]]

Any chance you still have the stacktrace?
It's looking like a kotlinx-coroutines bug that just happens to hit Arrow code, but I'm not sure. The relevant Arrow code looks like a natural mix of coroutines primitives. The only suspicious part might be the either { semaphore.withPermit { ... } }, which maybe should be nested the other way around. I doubt that's the issue though. I don't think the nesting is observable in this case really.

[Youssef Shoaib [MOD]]

Especially if there's a Caused By I'd love to go thru that

[Youssef Shoaib [MOD]]

I believe the error message is referencing kotlinx-coroutines maintainers FWIW

[simon.vergauwen]

lease read KDoc to 'handleFatalException' method and report this incident to maintainers

Yes, this is from KotlinX Coroutines not from us

[Kev]

It turns out that there was a gradle dependency forcing itself to a lower version of the coroutine dependency. Even though I’m using the bom, the other dependency’s rule was overriding the bom’s version.

enforcedPlatform didn’t solve the problem. I had to create a configuration block and force each dependant to the coroutine version

[simon.vergauwen]

@Kev so after this gradle dependency fix it was solved?

[Kev]

@simon.vergauwen correct