Unnecessary backoff and dubious sleep delay
norinorin opened this issue · comments
Shouldn't it just continue at the last iteration instead of sleeping? It seems redundant to wait for n seconds just to raise the error; also, according to the docs, the retry-after header returns the millisecond timeout. Though, this lib treats it as seconds. Which one is correct?
Expected Behavior
It does the backoff only at the first iteration.
Current Behavior
It does the backoff at both iterations.
According to top-gg/docs#46, it's indeed in seconds.