-
Notifications
You must be signed in to change notification settings - Fork 726
0.23.26: Detect and error on faulty io::Write::write_vectored
#2422
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
Conversation
Benchmark resultsInstruction countsSignificant differencesThere are no significant instruction count differences Other differencesClick to expand
Wall-timeSignificant differencesClick to expand
Other differencesClick to expand
Additional informationCheckout details:
|
Codecov ReportAll modified and coverable lines are covered by tests ✅
Additional details and impacted files@@ Coverage Diff @@
## main #2422 +/- ##
=======================================
Coverage 96.01% 96.01%
=======================================
Files 94 94
Lines 22558 22567 +9
=======================================
+ Hits 21658 21667 +9
Misses 900 900 ☔ View full report in Codecov by Sentry. 🚀 New features to boost your workflow:
|
Do we want to get out a release for this? |
Thanks for the quick fix! |
73c918e
to
25e11b4
Compare
Yep! Have added a bump commit and release notes to this PR. |
io::Write::write_vectored
io::Write::write_vectored
fixes #2316
Release notes for 0.23.26
std::io::Write::write_vectored
implementations that reported writing more bytes than were available, in violation of that method's invariants. This seems to happen on macOS with certain VPN software active. Now we detect and return an error fromwrite_tls
calls in this case. See Panic inwrite_tls
#2316.SignatureScheme
s in TLS1.3, so that external providers may support ED448, post-quantum signatures, and others. See Invert working ofSignatureScheme::supported_in_tls13
#2420.