o ɶd!@sddlmZmZmZddlmZddlmZddlmZ ddl Z ddl Z e e ZgdggdZGd d d eZGd d d eZGd ddeZGdddeZGdddeZdS)) ServiceErrorRequestExceptionConnectTimeout)CircuitBreakerError)Timeout)ConnectionErrorNIncorrectStateiic@s*eZdZdZddZddZd ddZdS) RetryCheckerContainera A container which holds at least one retry checker. This lets us chain together different retry checkers into an overall evaluation of whether we should retry a request. Checkers are evaluated in the order they appear in the provided list of checkers, and if one checker reports failure we consider this to be an overall failure and no more retries should happen. cKs|std||_dS)Nz/At least one retry checker needs to be provided) ValueErrorcheckers)selfrkwargsr= 1, with 1 indicating no retriesr)r r'r0r max_attempts)rr3rr)rrrss zLimitBasedRetryChecker.__init__NcKr+)NZcurrent_attemptr)r3r,r"rrrrzr-z#LimitBasedRetryChecker.should_retry)r1rr.rrr)rr0is r0cs>eZdZdZgdggdZedffdd Zd dd ZZS) ,TimeoutConnectionAndServiceErrorRetryCheckera A checker which will retry on certain exceptions. Retries are enabled for the following exception types: - Timeouts from the requests library (we will always retry on these) - ConnectionErrors from the requests library (we will always retry on these) - Built-in ConnectionErrors from Python 3 - Service errors where the status is 500 or above (i.e. a server-side error, except 501) - Service errors where a status (e.g. 429) and, optionally, the code meet a given criteria The last item is configurable via dictionary where the key is some numeric status representing a HTTP status and the value is a list of strings with each string representing a textual error code (such as those error codes documented at https://docs.cloud.oracle.com/Content/API/References/apierrors.htm). If an empty list is provided, then only the numeric status is checked for retry purposes. For a populated array, we are looking for where the numeric status matches and the code from the exception appears in the array. As an example: .. code-block:: python { 400: ['QuotaExceeded'], 500: [] } If no configuration is provided, then the default for service errors is to retry on HTTP 409/IncorrectState, 429's and 5xx's (except 501) without any code checks. If a specific 5xx code (e.g. 500, 502) is provided in the dictionary, then it takes precedence over the option to retry on any 500, for example, it is possible to retry on only 502s (either by status or by status and matching some code) by disabling the general "retry on any 5xx" configuration and placing an entry for 502 in the dictionary r r Tc s&tt|jdi|||_||_dSr&)r'r4r retry_any_5xxservice_error_retry_config)rr6r5rr)rrrs z5TimeoutConnectionAndServiceErrorRetryChecker.__init__NcKst|trdSt|trdSt|trdSt|trdSt|tr3d|vr1tj|d|fddSt|t r^|j |j vrM|j |j }|sHdS|j |vS|j r\|j dkr\|j dkr\dSdSz t|trgWdSWdStysYdSw)NTZcircuit_breaker_callback)targetargsiiF) isinstancerRequestsConnectionErrorrrr threadingThreadstartrstatusr6coder5r NameError)rrrrcodesrrrrs<            z9TimeoutConnectionAndServiceErrorRetryChecker.should_retryr)rrrrRETRYABLE_STATUSES_AND_CODESrrr/rrr)rr4~sr4) exceptionsrrrZcircuitbreakerrZoci._vendor.requests.exceptionsrrr:loggingr; getLoggerrloggerrBobjectr r r$r0r4rrrrs     '