TooManyRequestsError has no reconnect hint

[xiaoshenxian]

I found you throw TooManyRequestsError for error code 429 which should contain a header named 'Retry-After' for retry waiting seconds. This can be retreived by the old mono API, but cannot be retreived by the new one since the TooManyRequestsError contains only a message.

[xiaoshenxian]

Maybe you can schedule a retry directly in binance_common.util.send_request when you received a 429.

[AyeshaNasirWebDeveloper]

Hi @xiaoshenxian, I’d like to work on this issue if no one is currently working on it. I can investigate how the 429 response and Retry-After header are currently handled, then update TooManyRequestsError to expose the retry information and add appropriate tests.

Please let me know if it’s okay for me to submit a PR for this issue.

[alplabin]

Hi @xiaoshenxian,
A new release of binance-common (v4.4.0) has been made which update the TooManyRequestsError error and include retry_after info. Please give it a try and let us know if you encounter any issue.