Hi Ralf,

I pushed changeset:   8630:9311bb32ddf0
which changed the exception handling. It's a small change and passed CI.
Can you pull it and see if it helps.

I haven't tried reproducing issue2551225, but if I am reading it correctly,
there should be an error logged now.

The commit message is:

Changed exception handling in two places.

There is an inner try/except where I added the more specific
ConnectionAbortedError before the existing IOError
exception. ConnectionAbortedError should be what is returned (in
python 3) when writing on a closed connection caused by the client
going away. Unable to test though.

Then I set up IOError to log/report exception as it is
unexpected. This logs useful error for the issue.

In the outer try/except, I replaced outer IOError handler with
ConnectionAbortdError handler. Then I removed IOError handler and let
an IOError fall through the last resort exception handler.

For this specific translator issue, generating the html error message
also crashes because it is trying to translate it and translation
fails. So I wrap the cgitb.http call in try/except Exception and
logger.exception() the original exception so there is something useful
logged.

Thanks.

-- rouilj