MultiplexingStream should transmit error condition that shuts down channels #299
Comments
|
Talk to @sharwell before fixing this if we end up throwing on the reader side where we used to just report the end of a stream, because that's a behavior-breaking change that could screw up roslyn. |
AArnott
pushed a commit
that referenced
this issue
Nov 12, 2024
Bumps [Nerdbank.GitVersioning](https://github.com/dotnet/Nerdbank.GitVersioning) from 3.6.143 to 3.6.146. - [Release notes](https://github.com/dotnet/Nerdbank.GitVersioning/releases) - [Commits](https://github.com/dotnet/Nerdbank.GitVersioning/commits) --- updated-dependencies: - dependency-name: Nerdbank.GitVersioning dependency-type: direct:production update-type: version-update:semver-patch ... Signed-off-by: dependabot[bot] <[email protected]> Co-authored-by: dependabot[bot] <49699333+dependabot[bot]@users.noreply.github.com>
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
When a channel's
PipeReaderorPipeWritercompletes with an exception, that closes the channel in a way that cannot be distinguished by the remote party from a completion without exception. In effect, an error on one side results in truncated data on the other side without any kind of warning.The text was updated successfully, but these errors were encountered: