fix(oauth): reset rate limit earlier in refresh cycle #158
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
reset rate limit as soon as we encounter a low rate limit, rather than once we finish retrieving a new token
if this doesn't work, my next choice is a single thread owning write access to
OAUTH_CLIENT
that can receive a reset signal from anywhere, and keeps track of the rate limits to allow both the expiry event and the rate limit event to reset it, without causing concurrent token retrievals