-
-
Notifications
You must be signed in to change notification settings - Fork 1.3k
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
bug: Very high false positive rate due to API key rate limiting #58
Comments
Could fix if we decied to use the bandaid in #50 . Let me know and I'll get it added. |
Fixed in #54. |
Issue is not fixed, still happening (but very rarely at the moment). Exact same problem. Here's the commit I'm on:
And here's a screenshot that gets generated: |
This was referenced Sep 20, 2020
jef
pushed a commit
that referenced
this issue
Sep 20, 2020
Co-authored-by: Lukas Szimtenings <[email protected]>
Closing as the implementation described is no longer in use. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Description
I just got the script and tried it with this
.env
:Every 30 seconds (about every 5 requests) I get a false positive because the page returns
Rate limit exceeded for API_KEY [9485fa7b159e42edb08a83bde0d83dia]
. (Confirmed this by looking at the screenshot it took.)Possible solution
Ignore the page when it says "Rate limit exceeded". Maybe print a warning to console too.
The text was updated successfully, but these errors were encountered: