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

bug: Very high false positive rate due to API key rate limiting #58

Closed
serg06 opened this issue Sep 19, 2020 · 4 comments · Fixed by #98
Closed

bug: Very high false positive rate due to API key rate limiting #58

serg06 opened this issue Sep 19, 2020 · 4 comments · Fixed by #98
Assignees

Comments

@serg06
Copy link
Contributor

serg06 commented Sep 19, 2020

Description

I just got the script and tried it with this .env:

NOTIFICATION_TEST="false"
PAGE_TIMEOUT="30000"
RATE_LIMIT_TIMEOUT="5000"
STORES="nvidia"

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.

@serg06 serg06 added the bug label Sep 19, 2020
@geman220
Copy link
Contributor

Could fix if we decied to use the bandaid in #50 . Let me know and I'll get it added.

@jef
Copy link
Owner

jef commented Sep 19, 2020

Fixed in #54.

@jef jef closed this as completed Sep 19, 2020
@serg06
Copy link
Contributor Author

serg06 commented Sep 19, 2020

Issue is not fixed, still happening (but very rarely at the moment). Exact same problem.

Here's the commit I'm on:

C:\repo\nvidia-snatcher>git log -n 1
commit 3b2ba29cf1c90bdfc98f3d3a042160a6d9c9601f (HEAD -> main, origin/main, origin/HEAD)
Author: Gylfi <gylli251@gmail.com>
Date:   Sat Sep 19 15:23:49 2020 +0000

    chore(store): add bandh links (#65)

    Co-authored-by: Jef LeCompte <jeffreylec@gmail.com>

And here's a screenshot that gets generated:

success-1600537744120

jef pushed a commit that referenced this issue Sep 20, 2020
Co-authored-by: Lukas Szimtenings <lszimtenings@ukaachen.de>
@jef jef reopened this Sep 23, 2020
@andrewmackrodt
Copy link
Contributor

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
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

4 participants