Uh oh!
There was an error while loading. Please reload this page.
Fix incorrect io::Take's limit resulting from io::copy specialization - #79650
Merged
Conversation
rust-highfive
commented
Dec 2, 2020
Contributor
r? @dtolnay (rust-highfive has picked a reviewer for you, use r? to override) |
dtolnay
approved these changes
Dec 5, 2020
dtolnay
commented
Dec 5, 2020
Member
@bors r+ |
bors
commented
Dec 5, 2020
Collaborator
📌 Commit a9b1381 has been approved by |
bors
commented
Dec 6, 2020
Collaborator
bors
commented
Dec 6, 2020
Collaborator
☀️ Test successful - checks-actions |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for freeto join this conversation on GitHub.
Already have an account?
Sign in to comment
5 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
The specialization introduced in #75272 fails to update
io::Takewrappers after performing the copy syscalls which bypass those wrappers. The buffer flushing before the copy does update them correctly, but the bytes copied after the initial flush weren't subtracted.The fix is to subtract the bytes copied from each
Takein the chain of wrappers, even when an error occurs during the syscall loop. To do so theCopyResultenum now has to carry the bytes copied so far in the error case.