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
I have the following retrying logic to retry only when a http call gets a 429. The retry happens in an unintuitive way: instead of calling the whole retryableRequest functions, it only calls the mapResponse. Only resp <- mapResponse(sttpResp, sttpResp.body.merge) is being used in the for comprehension of the retryable function, which is the one capturing the failure from mapResponse. Is this a normal behavior?
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
-
I have the following retrying logic to retry only when a http call gets a 429. The retry happens in an unintuitive way: instead of calling the whole retryableRequest functions, it only calls the mapResponse. Only
resp <- mapResponse(sttpResp, sttpResp.body.merge)
is being used in the for comprehension of the retryable function, which is the one capturing the failure from mapResponse. Is this a normal behavior?Beta Was this translation helpful? Give feedback.
All reactions