You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Would be useful to have a {purrr} adverb that is similar to {httr2}'s req_retry().
I think(?) adding a max_tries = Inf (or NULL default) param to insistently() wouldn't scope-creep too much, and let insistently() signal the (final) error once the retry count is exhausted.
An motivating use case is wrapping a function that delegates to some system call (e.g. via {processx}) that itself might be making network calls with some potential failure rate. (My particular instance of this is with wrapping some AWS CLI calls, which can fail due to intermitent network issues.)
The text was updated successfully, but these errors were encountered:
I think we're now somewhat moving away from these adverbs (in hindsight their names seem too clever), but I'll probably implement with_retries() shortly.
Would be useful to have a {purrr} adverb that is similar to {httr2}'s
req_retry()
.I think(?) adding a
max_tries = Inf
(orNULL
default) param toinsistently()
wouldn't scope-creep too much, and letinsistently()
signal the (final) error once the retry count is exhausted.An motivating use case is wrapping a function that delegates to some system call (e.g. via {processx}) that itself might be making network calls with some potential failure rate. (My particular instance of this is with wrapping some AWS CLI calls, which can fail due to intermitent network issues.)
The text was updated successfully, but these errors were encountered: