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
MAX_RETRY_SECONDS is also an important constant in the code for specifying the duration to stop the throttling retries.
However, there's no mention about same in the documentation.
Ideally, it should also be mentioned about in the documentation so that the user is aware about it.
The documentation should talk about the reason for keeping this current hardcoded value of 5s & it's usage (for e.g. in retry logic and backoff logic) etc.
Have a look at #21 and the discussion within. You will see some more info there about what is going on with different retry settings, and how MAX_RETRY_SECONDS effects the outputs. That PR has not been merged and it doesn't look like it will, so if you want the behaviour you suggest, I would suggest you use my fork which fixes this issue and uses a more suitable value of 60 seconds for MAX_RETRY_SECONDS.
MAX_RETRY_SECONDS is also an important constant in the code for specifying the duration to stop the throttling retries.
However, there's no mention about same in the documentation.
Ideally, it should also be mentioned about in the documentation so that the user is aware about it.
The documentation should talk about the reason for keeping this current hardcoded value of 5s & it's usage (for e.g. in retry logic and backoff logic) etc.
Relates to - #36
The text was updated successfully, but these errors were encountered: