HTTP/3: QuicStream.ReadAsync ignores abort?

[JamesNK]

I have a server-to-client unidirectional stream. The server aborts its stream with AbortWrite(Error)

The client stream then calls ReadAsync and it returns a read count of 0. This is unexpected. Usually, a read count of 0 indicates successfully reading to the end of the stream. I expected an aborted exception instead.

When I look at the client stream's internal state I can see that it received the error code (ReadErrorCode):

Is this intended? I haven't tested whether this happens in other stream scenarios (client-to-server bidirectional and client-to-server unidirectional).

[ghost]

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

Issue Details

---

I have a server-to-client unidirectional stream. The server aborts its stream with:

_stream.AbortRead(Error);
_stream.AbortWrite(Error);

(AbortRead call is probably unnecessary, but I'm guessing it's not the cause of this issue)

The client stream then calls ReadAsync and returns 0 (which usually indicates successfully reading to the end of the stream). I expected an aborted exception instead.

When I look at the client stream's internal state I can see that it received the error code (ReadErrorCode):

Is this intended?

Author:	JamesNK
Assignees:	-
Labels:	area-System.Net.Quic
Milestone:	-

[JamesNK]

stream.ReadAsync does throw QuicStreamAbortedException for client-to-server unidirectional stream on AbortWrite.

Is the bug unique to reading from server-to-client unidirectional streams?

[ManickaP]

This should work as you say, we should investigate and fix that.

Haven't we done some work in handling aborts for ReadAsync? cc: @CarnaViire

[wfurt]

This may be fixed with #54798 as we set _canRead to false so ReadAsync will throw.
We should probably add explicit test and agree that the InvalidOperationException is good enough (or we should be smarter about exception type)

[JamesNK]

This might be a duplicate of #53530

[JamesNK]

This is a race condition. The test correctly threw QuicStreamAbortedException once.

[ManickaP]

Duplicate of #53530