Skip to content
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

Jump to bottom

When using a single channel among multiple workers, only one channel will ever observe a channel's close #3733

Closed
p6rt opened this issue Mar 15, 2015 · 4 comments
Closed

When using a single channel among multiple workers, only one channel will ever observe a channel's close #3733

p6rt opened this issue Mar 15, 2015 · 4 comments

Comments

@p6rt
Copy link

p6rt commented Mar 15, 2015

Migrated from rt.perl.org#124071 (status was 'resolved')

Searchable as RT124071$
@p6rt
Copy link
Author

p6rt commented Mar 15, 2015

From @hoelzro

If you use a channel to distribute work among several worker tasks (as in the attached example), only one worker will observe the close event on the channel after all of the work has been pushed into the channel. The remaining workers will block indefinitely, and awaiting them will block as well.

@p6rt
Copy link
Author

p6rt commented Mar 15, 2015

From @hoelzro

single-channel-many-readers.p6

@p6rt
Copy link
Author

p6rt commented Mar 15, 2015

From @hoelzro

On Sun Mar 15 12​:56​:43 2015, rob@​hoelz.ro wrote​:

If you use a channel to distribute work among several worker tasks (as
in the attached example), only one worker will observe the close event
on the channel after all of the work has been pushed into the channel.
The remaining workers will block indefinitely, and awaiting them will
block as well.

Fixed in rakudo/rakudo@f19bea1.

@p6rt p6rt closed this as completed Mar 15, 2015
@p6rt
Copy link
Author

p6rt commented Mar 15, 2015

@hoelzro - Status changed from 'new' to 'resolved'

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@p6rt