Windows builds are failing the culling test

[blink1073]

Description

I reran https://github.com/jupyter-server/jupyter_server_terminals/runs/4960949698?check_suite_focus=true, which had originally passed. It might be related to the 2.0.1 pywinpty release.

I confirmed that pinning to pywintpy<2 allows us to cull again. Merging #6 with a workaround for now.

[welcome]

Thank you for opening your first issue in this project! Engagement like this is essential for open source projects! 🤗

If you haven't done so already, check out Jupyter's Code of Conduct. Also, please try to follow the issue template as it helps other other community members to contribute more effectively.

You can meet the other Jovyans by joining our Discourse forum. There is also an intro thread there where you can stop by and say Hi! 👋

Welcome to the Jupyter community! 🎉

[blink1073]

The difference is that we are not triggering an eof on the pty. In the working version, we get the logs:

INFO     ServerApp:management.py:217 EOF on FD 1360; stopping reading
INFO     ServerApp:management.py:382 Terminal 1 closed

management.py is in terminado. I'm going to look into adding a test to terminado that fails, and try and address the issue there.