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.

Sign up for GitHub

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

Dropping a oneshot sender does not wake the receiver #44

Closed
maxbrunsfeld opened this issue Jul 2, 2021 · 2 comments · Fixed by #50
Closed

Dropping a oneshot sender does not wake the receiver #44

maxbrunsfeld opened this issue Jul 2, 2021 · 2 comments · Fixed by #50
Milestone
0.5.0

Comments

@maxbrunsfeld
Copy link

maxbrunsfeld commented Jul 2, 2021 •
edited

With mpsc channels, if I drop all the senders, any outstanding recv calls will return an error. But with oneshot channels, this doesn't seem to happen; when I drop the sender, an outstanding recv call will just hang. Is it intentional that the behavior of oneshot channels differs from mpsc channels in this regard?
@austinjones austinjones linked a pull request Apr 13, 2022 that will close this issue
Fix a oneshot::Sender disconnect bug #50
Merged
@austinjones austinjones added this to the 0.5.0 milestone Apr 14, 2022
@austinjones
Copy link
Owner

Thanks for the report! This is fixed in v0.5.0 and is up on crates.io.

@maxbrunsfeld
Copy link
Author

Awesome, thank you!

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
0.5.0
Development

Successfully merging a pull request may close this issue.

Fix a oneshot::Sender disconnect bug austinjones/postage-rs
2 participants
@maxbrunsfeld @austinjones