Todd Sankey

Thanks @ahopkins . As a bit of additional information, the side effect that caused me to notice this is that when I run with multiple workers over a unix socket,...

I manually tried building with different options by changing [here](https://github.com/MagicStack/uvloop/blob/96b7ed31afaf02800d779a395591da6a2c8c50e1/Makefile#L42). It seems to be the differences caused by the UVLOOP_DEBUG flag that cause the tests to start failing.

I have been experiencing failures when under heavy load. This started with the aiohttp/aiohappyeyeballs changes in that projects 3.10.0 release. After some deep-diving I think the key change was that...

> @todddialpad very nice! Do you know does it help with the other issue #506 which seems to be also related to incorrect sharing of sockets etc? > > Any...

> > @todddialpad very nice! Do you know does it help with the other issue #506 which seems to be also related to incorrect sharing of sockets etc? > >...

Is accepting this blocked on the tests that are failing? I don't think those failures are related to this change, as they are also failing for PR #644, which is...

@fantix thanks for having a look at this. I am not sure what to make of the test failures. The failures seem to be all related to Unix transports and...

> * Tests / test (3.12, macos-latest) (pull_request) Yes, I get the failures with the debug build, good eye. Thanks. I have instrumented the changed code, and in a failing...

> So, could an upstream dependency have broken the debug build? Since the last successful test run, the following upstream dependencies have changed: ``` Cython-3.1.0 (was 3.0.12) aiohttp-3.11.18 (was 3.11.16)...

> Would a manual execution of the tests on the main branch still pass (assuming it will grab Cython 3.1.0)? I forked the main branch and tried running the tests....