fix: EOF error on piped stderr being closed on Windows

Problem: An EOF error happens when creating a subprocess Nvim instance
on Windows. All CI tests are failing, and `attach('child', ...)` cannot
be run.

Solution: Ignore pipe_connection_lost error, and do not close the
asyncio event loop. Since embedded nvim only expects to use stdin and
stdout only as a msgpack-RPC channel, it's fine to ignore broken pipes
on the stderr.

Fixes #505

Author: wookayin

pynvim/msgpack_rpc/event_loop/asyncio.py

@@ -60,12 +60,17 @@ def data_received(self, data: bytes) -> None:
 
     def pipe_connection_lost(self, fd, exc):
         """Used to signal `asyncio.SubprocessProtocol` of a lost connection."""
+        debug("pipe_connection_lost: fd = %s, exc = %s", fd, exc)
+        if os.name == 'nt' and fd == 2:  # stderr
+            # On windows, ignore piped stderr being closed immediately (#505)
+            return
         self._on_error(exc.args[0] if exc else 'EOF')
 
     def pipe_data_received(self, fd, data):
         """Used to signal `asyncio.SubprocessProtocol` of incoming data."""
         if fd == 2:  # stderr fd number
-            self._on_stderr(data)
+            # Ignore stderr message, log only for debugging
+            debug("stderr: %s", str(data))
         elif self._on_data:
             self._on_data(data)
         else: