@OOfHdZGddeZGddeZGddeZGddeZGd d eZGd d eZGd deZy)a Edit 2020-12 @mhils: The advice below hasn't paid off in any form. We now just use builtin exceptions and specialize where necessary. --- We try to be very hygienic regarding the exceptions we throw: - Every exception that might be externally visible to users shall be a subclass of MitmproxyException.p - Every exception in the base net module shall be a subclass of NetlibException, and will not be propagated directly to users. See also: http://lucumr.pocoo.org/2014/10/16/on-error-handling/ c$eZdZdZdfd ZxZS)MitmproxyExceptionz< Base class for all exceptions thrown by mitmproxy. c$t||yN)super__init__)selfmessage __class__s U/var/www/premiumrankchecker/venv/lib/python3.12/site-packages/mitmproxy/exceptions.pyrzMitmproxyException.__init__s !r)__name__ __module__ __qualname____doc__r __classcell__)r s@r rrs""r rc eZdZy)FlowReadExceptionNr rrr r rrr rc eZdZy)ControlExceptionNrrr r rr rr rc eZdZy) CommandErrorNrrr r rr$rr rc eZdZy) OptionsErrorNrrr r rr(rr rc eZdZy)AddonManagerErrorNrrr r rr,rr rceZdZdZy) AddonHaltzW Raised by addons to signal that no further handlers should handle this event. N)r rrrrr r r r 0sr r N) r Exceptionrrrrrrr rr r r"sc$"" *  )  9  %  * "r