[10.x] allow $sleepMilliseconds
parameter receive a Closure in retry
method from PendingRequest
#46653
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
The
retry
helper accepts either anint
or aClosure
. When passing aClosure
object, the$attempts
and the$exception
would be passed, allowed users to implement their own backoff algorithm. Theretry
helper is used in the Pending Request class to perform request retries as well, but in this specific local, the parameters are sent after being informed byretry
method that belongs to the same class mentioned, and in this method, is not accepted to inform$sleepMilliseconds
as aClosure
.This pull request will allows you to inform
$sleepMilliseconds
parameter as aClosure
orint
, opening the possibility to create your own backoff algorithm for retry requests.Example use case
Imagine a scenario where it is necessary to perform a backoff when the exception returned is of type
Request Timeout (408)
, with this modification it would be possible to implement a dynamic strategy as follows: