Hey guys, I think there is a problem when calling

join

on an exceptionally completed job. After days digging, I figure out that if the

join

call falls into the fast-path or successfully suspending, a CancellationException will be thrown in this case, but if the

join

call falls into the

joinSuspend

path but not successfully suspending, no CancellationException will happen. I just wonder that is it a bug to get inconsistent result from

join

with the same code? I have created a gist here https://gist.github.com/enbandari/0321cffa792e0f98d90e0e77682aeaed to make it more clear.

Probably best to file an issue for this

Okay. 😅

Thanks for report. There is indeed a race in

join

. Fixing it.

👍