You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I am enjoying the results of the work you have done on this library. Thank you for it. I have one question. I am trying to drain multiple channels into one and when I use Select#selectOrClosed in a loop I encounter a situation that from the point a single channel gets closed I only ever get a ChannelDone out. The following is the behavior captured in a unit test.
If I want to avoid this problem I have to remove closed channels from the list being selected on every iteration. I captured this in a unit test as well:
I have to loop through all of the channels because unfortunately the ChannelDone signal does not have a reference to the channel that it relates to :(.
My question is: Is this the correct behavior or am I doing something silly?
Thanks!
The text was updated successfully, but these errors were encountered:
Yes, it's a shortcoming I'm hoping to address sooner rather than later :) That's how we're using channels too (filtering out the "done" ones if needed)
Hi team!
I am enjoying the results of the work you have done on this library. Thank you for it. I have one question. I am trying to drain multiple channels into one and when I use
Select#selectOrClosed
in a loop I encounter a situation that from the point a single channel gets closed I only ever get aChannelDone
out. The following is the behavior captured in a unit test.If I want to avoid this problem I have to remove closed channels from the list being selected on every iteration. I captured this in a unit test as well:
I have to loop through all of the channels because unfortunately the
ChannelDone
signal does not have a reference to the channel that it relates to :(.My question is: Is this the correct behavior or am I doing something silly?
Thanks!
The text was updated successfully, but these errors were encountered: