[issue47071] asyncio proactor udp transport stops responding after send to port that isn't listening

Erik Soma added the comment: Certainly: https://github.com/python/cpython/pull/32011 -- ___ Python tracker ___ ___

[issue47071] asyncio proactor udp transport stops responding after send to port that isn't listening

Change by Erik Soma : -- keywords: +patch pull_requests: +30099 stage: -> patch review pull_request: https://github.com/python/cpython/pull/32011 ___ Python tracker ___

[issue47071] asyncio proactor udp transport stops responding after send to port that isn't listening

Andrew Svetlov added the comment: Thanks for the report. Could you make a pull request? The whole attached windows_events.py is hard to analyze. -- ___ Python tracker ___

[issue47071] asyncio proactor udp transport stops responding after send to port that isn't listening

Erik Soma added the comment: Uploading my hack to `asyncio.windows_events.py` -- this is based off 3.10.2's distribution. -- Added file: https://bugs.python.org/file50692/windows_events.py ___ Python tracker

[issue47071] asyncio proactor udp transport stops responding after send to port that isn't listening

New submission from Erik Soma : Reproducer attached. Change `USE_PROACTOR` to `False` to use the `SelectorEventLoop` instead, which doesn't exhibit this behavior. The output on my machine when using the proactor loop is: ``` datagram received b'ping 1' datagram received b'ping 2' ``` And the