-
-
Notifications
You must be signed in to change notification settings - Fork 2.5k
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
bugfix: Remove erroneous wake call in SinkWriter #5436
bugfix: Remove erroneous wake call in SinkWriter #5436
Conversation
cc @Darksonn |
78b1da0
to
28d294c
Compare
Per review comment tokio-rs#5070 (comment): > Adding a wake call here will be a busy loop that consumes 100% CPU > waiting for it to become ready. We shouldn't do that. Furthermore, according to https://docs.rs/futures-sink/latest/futures_sink/trait.Sink.html#tymethod.poll_ready, poll_ready will make sure that the current task is notified. Discussion: https://discord.com/channels/500028886025895936/500336346770964480/1072534504981418024
28d294c
to
33e7e91
Compare
Co-authored-by: Alice Ryhl <aliceryhl@google.com>
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thanks.
Note that this bug never appeared in a published release. |
Hello! Is it possible to copy discussion from discord (or provide summary) here? |
Sure, here is the discussion:
|
Per review comment #5070 (comment):
Furthermore, according to https://docs.rs/futures-sink/latest/futures_sink/trait.Sink.html#tymethod.poll_ready, poll_ready will make sure that the current task is notified.
Discussion: https://discord.com/channels/500028886025895936/500336346770964480/1072534504981418024