Ahmet Ibrahim Aksoy
Ahmet Ibrahim Aksoy
Can this be related to #102699? Actual issue seems that one of the streams is stuck(?) somewhere while reading, and it causes a `TimeoutException` but 100 seconds is still too...
> are we seeing any recent failures on 8.0? if yes, then we can try backporting the change Yes, in June we have 2 failures on 8.0, June 5th, June...
Triage: This is fixed in main (9.0) and hitting 2-3 times (low impact) per month in 8.0, closing this for now. If this issue bothers 8.0 so high, we can...
This should be fixed by #102699. I don't see any `TimeoutException` on Kusto in main within last 30 day as well (only handshake timeouts on QUIC which can be too...
Original bug fixed by #102699 in main. For handshake timeouts closing this in favor of #104426.
@MihaZupan I believe this one is also fixed by #102699. Only failure I've seen from main is 1.5 months ago and it was `TimeoutException`. I'd say we can safely close...
> Triage: there's ~1 failure per month and it's highly likely test bug. We might decide to push this into future. I saw last occurrence on 3/27, and it failed...
Duplicate of #101377
My inital guess related to this is: https://github.com/dotnet/runtime/blob/72d00a898c3e63247d5a87793ed8a912b65da451/src/libraries/System.Net.Http/src/System/Net/Http/SocketsHttpHandler/Http2Connection.cs#L304-L306 First comment is happening, just before `Shutdown`. I'm not sure if this is expected behavior but looks like this is happening when...
No failure or re-runs `Http1MultiChunkResponseStreamZeroByteReadTest.ZeroByteRead_IssuesZeroByteReadOnUnderlyingStream` within 30 days in main, reported issue in the table is from `release/8.0-staging`. Closing the issue, we can re-open if needed.