-
Notifications
You must be signed in to change notification settings - Fork 63
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
Support resuming #53
Comments
This would be a great addition. I'd need to dig some more into the On the surface, however, after a quick research, it seems like I might have made a little implementation mistake at this location: useful-forks.github.io/website/src/queries-logic.js Lines 337 to 342 in 90dc02a
I think I could increase the retry count, and the useful-forks.github.io/website/src/queries-logic.js Lines 120 to 124 in 90dc02a
I'll probably get back on it eventually, but feel free to dig into it yourself and provide a PR if you want this feature to be implemented quickly. :) Side-note: additionally, that retry should probably also display that timer slider animation. |
I did run useful-forks on repo that has >5000 forks, and naturally got
GitHub API rate-limits exceeded
. It would be nice if there would be a way (button?) to resume scanning after waiting long enough to be no longer blocked on API calls. I tried editing access token to re-save it, but it did not resume activities.The text was updated successfully, but these errors were encountered: