Skip to content

[release/6.0] Fixed StreamPipeReader.CopyToAsync - #57965

Closed
github-actions[bot] wants to merge 2 commits into
release/6.0from
backport/pr-57943-to-release/6.0
Closed

[release/6.0] Fixed StreamPipeReader.CopyToAsync#57965
github-actions[bot] wants to merge 2 commits into
release/6.0from
backport/pr-57943-to-release/6.0

Conversation

@github-actions

@github-actionsgithub-actionsBot commented Aug 23, 2021

Copy link
Copy Markdown
Contributor

Backport of #57943 to release/6.0

/cc @davidfowl

Customer Impact

We introduced a regression in StreamPipeReader when doing performance optimizations in .NET 6. This could lead to silent corruption of data when using the CopyToAsync method.

Testing

Unit testing.

Risk

Very Low.

…unt when copying buffered data. This handles the case where ReadAsync has consumed a partial segment and then the same PipeReader instance is used to copy to a Stream and PipeWriter. - Added tests
@ViktorHofer

Copy link
Copy Markdown
Member

@davidfowl just FYI, release/6.0-rc1 commits are automatically flowing into release/6.0 (rc2).

@davidfowl

Copy link
Copy Markdown
Member

Ah good.

@davidfowl

Copy link
Copy Markdown
Member

So I can close this.

@ViktorHofer
ViktorHofer deleted the backport/pr-57943-to-release/6.0 branch August 24, 2021 06:45
@ghostghost locked as resolved and limited conversation to collaborators Sep 23, 2021
Sign up for freeto subscribe to this conversation on GitHub. Already have an account? Sign in.

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants

@ViktorHofer@davidfowl@halter73