is_retryable_http_exception

Documentation for eth_defi.middleware.is_retryable_http_exception function.

is_retryable_http_exception(exc, retryable_exceptions=(<class 'requests.exceptions.ConnectionError'>, <class 'requests.exceptions.HTTPError'>, <class 'requests.exceptions.Timeout'>, <class 'requests.exceptions.TooManyRedirects'>, <class 'web3.exceptions.BlockNotFound'>, <class 'requests.exceptions.ChunkedEncodingError'>, <class 'http.client.RemoteDisconnected'>, <class 'eth_defi.middleware.SomeCrappyRPCProviderException'>, <class 'requests.exceptions.ContentDecodingError'>), retryable_status_codes=(429, 500, 502, 503, 504, 525, 520, 410, 403, 400), retryable_rpc_error_codes=(-32003, -32043, -32005, -32701, 42903, -32002, -32603, -32052, -32601), retryable_rpc_error_messages={'Internal JSON-RPC error', 'Parse error', 'Unexpected error (code=40000)', 'empty reader set', 'execution aborted (timeout = 5s)', 'header not found', 'nonce too low'}, method=None, params=None)

Helper to check retryable errors from JSON-RPC calls.

Retryable reasons are connection timeouts, API throttling and such.

We support various kind of exceptions and HTTP status codes we know we can try.

Parameters

• exc (Exception) – Exception raised by requests or Web3 machinery.

• retryable_exceptions (Tuple[BaseException]) – Exception raised by requests or Web3 machinery.

• retryable_status_codes (Collection[int]) – HTTP status codes we can retry. E.g. 429 Too Many requests.

• retryable_rpc_error_messages (Collection[str]) – See DEFAULT_RETRYABLE_RPC_ERROR_MESSAGES.

• method (str | None) – JSON-RPC method name we called.

• params (list | None) – Method args.

• retryable_rpc_error_codes (Collection[int]) –