-
-
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
chore: prepare Tokio v1.8.4 #4237
Conversation
Depends on #4226 ## Motivation Currently, the safety invariants and synchronization strategy used in `tokio::sync::oneshot` are not particularly obvious, especially to a new reader. It would be nice to better document this code to make these invariants clearer. ## Solution This branch adds `SAFETY:` comments to the `oneshot` channel implementation. In particular, I've focused on documenting the invariants around when the inner `UnsafeCell` that stores the value can be accessed by the sender and receiver sides of the channel. I still want to take a closer look at when the waker cells can be set, and I'd like to add more documentation there in a follow-up branch. Signed-off-by: Eliza Weisman <eliza@buoyant.io>
Ugh, the build's failing because there's other stuff that hasn't been backported to the LTS branch, that's cool. |
For time audit issue: d4848a9 |
Thanks for finding that <3 |
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.
Looks good!
MacOS is broken:
|
FreeBSD is also borked |
The borked tests were fixed in #3952 on master. |
Thanks, I'll grab that commit as well. |
In order to get the macros build tests to pass I had to basically cherry-pick every |
The tokio-macros crate has its own tags for its previous releases. |
1.8.4 (November 15, 2021)
This release backports a bug fix from 1.13.1.
Fixed
oneshot::Sender::send
and awaiting aoneshot::Receiver
when the oneshot has been closed (sync: fix racyUnsafeCell
access on a closed oneshot #4226)