Unexpected `QuicStream.WriteAsync` exception

[bentoi]

Description

QuicStream.WriteAsync can throw if the remote stream is disposed after reading the data. I don't expect WriteAsync to throw if the data is successfully sent.

Reproduction Steps

Run the attached test case: quicwriteexception.zip

Expected behavior

No exception.

Actual behavior

WriteAsync raises System.Net.Quic.QuicException: Stream aborted by peer (0).

Regression?

No response

Known Workarounds

No response

Configuration

DotNet 7.0.100

Other information

No response

Tagging subscribers to this area: @dotnet/ncl
See info in area-owners.md if you want to be subscribed.

Issue Details

---

Description

QuicStream.WriteAsync can throw if the remote stream is disposed after reading the data. I don't expect WriteAsync to throw if the data is successfully sent.

Reproduction Steps

Run the attached test case: quicwriteexception.zip

Expected behavior

No exception.

Actual behavior

WriteAsync raises System.Net.Quic.QuicException: Stream aborted by peer (0).

Regression?

No response

Known Workarounds

No response

Configuration

DotNet 7.0.100

Other information

No response

Author:	bentoi
Assignees:	-
Labels:	untriaged, area-System.Net.Quic
Milestone:	-

[CarnaViire]

Triage: I was able to reproduce it (though I had to wait for some time before that happened).
We need to fix it in 8.0.
Seems to be part of a group of issues around S.N.Quic's ResettableValueTaskSource (Cancellation, Reads/WritesClosed and disposal order/behavior).

[ManickaP]

I think this is similar to this test issue: #81944