Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

fix: check response for rate limiting (#58) #98

Merged
merged 4 commits into from
Sep 20, 2020
Merged

fix: check response for rate limiting (#58) #98

merged 4 commits into from
Sep 20, 2020

Conversation

lukszi
Copy link
Contributor

@lukszi lukszi commented Sep 20, 2020

Description

Fixes #58
The issue has been adressed previously, but not been fixed in it's entirety.
This PR fixes the issue by checking for a 429 HTTP response.

Testing

I ran the script for about half an hour with only the default configuration enabled.

@lukszi lukszi requested a review from jef as a code owner September 20, 2020 08:35
Copy link
Owner

@jef jef left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Looks good! Thanks for contributing!!!

@@ -11,6 +11,7 @@
"esModuleInterop": true,
"resolveJsonModule": true,
"skipLibCheck": true,
"forceConsistentCasingInFileNames": true
"forceConsistentCasingInFileNames": true,
"sourceMap": true
Copy link
Owner

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Nice -- been meaning to do that for some debugging.

@jef jef changed the title Fix #58 rare false positive on hitting rate limit fix: check response for rate limiting (#58) Sep 20, 2020
@jef jef merged commit b7d9462 into jef:main Sep 20, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

bug: Very high false positive rate due to API key rate limiting
2 participants