(Gj ldZddlmZddlZddlZddlmZejeZ e e e fZ dd Zdd ZdS)uSuppress benign event-loop teardown noise on the gateway serving loop. When the Desktop client forcibly closes its WebSocket while the gateway still has pending socket operations, asyncio's transport teardown logs a full traceback for every pending ``_call_connection_lost`` callback. On Windows this surfaces as ``ConnectionResetError: [WinError 10054]`` (and the rarer ``ConnectionAbortedError: [WinError 10053]``); on POSIX it is the equivalent ``ConnectionResetError``/``BrokenPipeError``. A single client disconnect can emit 50+ identical tracebacks into ``errors.log`` (#50005). These are not actionable — they are the expected side effect of the peer hanging up before our writes drained. We install a loop exception handler that collapses exactly this class of teardown error to one debug line and forwards everything else to asyncio's default handler unchanged, so genuine loop bugs still surface. ) annotationsN)Anycontextdict[str, Any]returnboolc|d}t|tsdS|d}|d}d}|t|vp|t|vS)u>True when the loop error is a peer-hangup during transport teardown. Gated on BOTH the exception type AND the ``_call_connection_lost`` callback so we only swallow the disconnect flood — any other place these errors surface (a real handler, a custom callback) still goes to the default handler. exceptionFcallbackhandle_call_connection_lost)get isinstance_BENIGN_TEARDOWN_ERRORSrepr)rexcr r markers ._handlerAsz w ' '  JJA K((    F   HT7 # # # # #  * *7 3 3 3 3 3rT)rrrrrr)getattrget_exception_handlerset_exception_handlerrAttributeError TypeError)rr!r s @rinstall_loop_noise_filterr'6s t5u==))++H 4 4 4 4 4 4 x((( .2+++ I &     sAA#"A#)rrrr)rrrr)__doc__ __future__rasynciologgingtypingr getLogger__name__rConnectionResetErrorConnectionAbortedErrorBrokenPipeErrorrrr'rrr3s"#"""""w"" >>>>&      r