Hi Ross:

I'm unable to generate a BrokenPipeError using the tools I have.

However, I do now understand the reason a BrokenPipeError generated
two more exceptions. The last resort Exception handler tries to report
the problem to the client. When the client is gone, it produces more
exceptions when writing to the closed socket.

I added the following near line 284 in roundup/scripts/roundup_server.py:

     except (BrokenPipeError, ConnectionAbortedError, ConnectionResetError) as e:
         self.log_info("Client has gone: %s", e)

right before:

    except Exception:

whose block includes the words "EXCEPTION AT".

Can you patch the code and verify that you do not get a traceback on a BrokenPipeError
and instead get a log message.

Thanks.

-- rouilj