Ahmet Ibrahim Aksoy
Ahmet Ibrahim Aksoy
@stephentoub I tried to make `GetOrCreateAcceptSocket` compatible with the Windows definition of this function, but in this way, we're creating an unnecessary socket when `acceptSocket?` is null. We'll copy the...
> Welcome to the repo @liveans Thank you very much!
I was able to reproduce the issue in main, .NET 7.0, 6.0 and 5.0. I think it should be easy to fix. Not critical. We can investigate it more deeply.
https://github.com/dotnet/runtime/blob/960e4d723c27a5407dc691d06e546bc455a9c4a5/src/libraries/System.Net.Sockets/src/System/Net/Sockets/Socket.Unix.cs#L139-L140 I think, this is the root cause of this issue. Because it's the only place that we can set the handle to -1 temporarily (via `CreateSocket`) outside of the...
The problem is race condition, actually. At the beginning of the `CreateSocket` function we have something like this: https://github.com/dotnet/runtime/blob/960e4d723c27a5407dc691d06e546bc455a9c4a5/src/libraries/System.Net.Sockets/src/System/Net/Sockets/SocketPal.Unix.cs#L59 Which means we're replacing the current `Socket` instance's handle with default...
@MichaelSimons also can you help here as well, if you have any information related with this?
This is only failing for HTTP/3. This test has been disabled with #94507 until now, and re-enabled on #100911, looks like it has the same root cause as #94507. I'm...
I changed the issue number on the test, closing this issue as a duplicate of #91757, and deleting the `disabled-test` label.
I will watch this issue in CI (main) for a while, and if it happens again, I'll re-open.