-
Notifications
You must be signed in to change notification settings - Fork 1.9k
ReceiveChannel.onReceiveOrClosed throws when selecting on already-closed channel #1584
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Labels
Comments
zach-klippenstein
added a commit
to square/workflow
that referenced
this issue
Oct 1, 2019
I think this fixes #626. Likely caused by Kotlin/kotlinx.coroutines#1584.
zach-klippenstein
added a commit
to square/workflow
that referenced
this issue
Oct 1, 2019
I think this fixes #626. Likely caused by Kotlin/kotlinx.coroutines#1584.
zach-klippenstein
added a commit
to square/workflow
that referenced
this issue
Oct 1, 2019
I think this fixes #626. Likely caused by Kotlin/kotlinx.coroutines#1584.
zach-klippenstein
added a commit
to square/workflow
that referenced
this issue
Oct 1, 2019
I think this fixes #626. Likely caused by Kotlin/kotlinx.coroutines#1584.
qwwdfsad
added a commit
that referenced
this issue
Oct 8, 2019
… a coroutine to avoid double resume Fixed #1584
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
When using
onReceiveOrClosed
(#330) to select on a channel that has already been closed, the select builder fails.Extremely simple to reproduce:
Exception:
Replacing
onReceiveOrClosed
withonReceiveOrNull
works as expected –null
is returned fromselect
and the program finishes normally.Versions:
Kotlin: 1.3.50
Coroutines: 1.3.1
The text was updated successfully, but these errors were encountered: