add httpx.ReadError handlers and throw them as OfflineException

[RTUnreal]

No description provided.

[RTUnreal]

I have checked the source code and concluded, the other exceptions where caught, but the ReadError was not. Should we make it more general and catch all httpx.NetworkErrors as OfflineExceptions @ldruschk?

I also think there were some issues with PoolTimeouts, but personally I didn't got these. @a-miscellaneous, can you tell which Exceptions were also not caught, but should be by the enochecker3?

[ldruschk]

I wanted to avoid catching too broad exceptions, to avoid masking checker errors that should be dealt with explicitly by checker authors (these should lead to checker errors when not explicitly handled). We should review the httpx-Exceptions and determine which are generic enogh to catch in the checker lib

[RTUnreal]

here is the tree of exceptions: https://www.python-httpx.org/exceptions/

• HTTPError
  • RequestError
    • TransportError
      • TimeoutException
        • ConnectTimeout
        • ReadTimeout
        • WriteTimeout
        • PoolTimeout
      • NetworkError
        • ConnectError
        • ReadError
        • WriteError
        • CloseError
      • ProtocolError
        • LocalProtocolError
        • RemoteProtocolError
      • ProxyError
      • UnsupportedProtocol
    • DecodingError
    • TooManyRedirects
  • HTTPStatusError
• InvalidURL
• CookieConflict
• StreamError
  • StreamConsumed
  • ResponseNotRead
  • RequestNotRead
  • StreamClosed

[a-miscellaneous]

IMO, the general issue is that the common use-case is not met. currently all errors are thrown as internal exceptions which is obviously not the case. Hence most would write a wrapper to handle exceptions, I personally got inspired by underleaf.

[RTUnreal]

tbh, that is a bit of a horrible way of dealing with exceptions. If a unintended exception occurs, then it should be handled like a checker error. And if there are more 'generic' Exceptions, then it should be dealt with as the correct exception.