Uncaught Exception (due to a data race) leads to process termination in Waitress
ImpactWaitress may terminate early due to a thread closing a socket while the main thread is about to call select(). This will lead to the main thread raising an exception that is not handled and then causing the entire application to be killed.PatchesThis issue has been fixed in Waitress 2.1.2 by no longer allowing the WSGI thread to close the socket, instead it is always delegated to the main thread.WorkaroundsThere is no work-around, however users using waitress behind a reverse proxy server are less likely to have issues if the reverse proxy always reads the full response.For more informationIf you have any questions or comments about this advisory:Open an issue in https://github.com/Pylons/waitress/issues (if not sensitive or security related)email the Pylons Security mailing list: [pylons-project-security@googlegroups.com](mailto:pylons-project-security@googlegroups.com) (if security related)