-
Notifications
You must be signed in to change notification settings - Fork 67
Yank all 0.2
versions older than 0.2.36
#107
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
Comments
Should we also yank all 0.1 versions? It seems like that 42bc921#diff-917ff224180b881299cdcef7bc14e710509229092ea4e6599861680bc0a2a458R65-R74 |
It has the same bug yes. We have not released any patch release fixing it for the |
Ping @jclulow ? |
I believe all of the older versions have been yanked. |
Amazing! Thank you. |
Due to #106. If the standard library ever do change the memory layout of
SocketAddr
, usage of this crate of versions before0.2.36
will have undefined behaviour and invalid memory access and lead to segfaults. And even if the standard library never do change the layout of those types, those versions of this crate still makes assumptions they should not.This is exactly what yanking is for. Marking a release as "should not be used". I think all versions of
net2
from0.2.0
through0.2.35
should be yanked from crates.io.Related issues on other crates having the same problem: rust-lang/socket2#139, tokio-rs/mio#1412
The text was updated successfully, but these errors were encountered: