policy-bot triggering Github abuse detection mechanism about policy-bot HOT 2 OPEN

Thanks for reporting this. I haven't actually seen the bot hit the abuse limits before, but we do implement conditional requests and caching to try to avoid regular rate limits (at least for the V3 API.)

Does this seem to happen more on certain types of webhook events? I'm curious if there is a particular handler where we're doing unnecessary work or if this is a consequence of necessary API requests combined with the rate at which PRs are opened.

from policy-bot.

It seems like we're hitting this more frequently internally. A recent example is a user navigating to the details page, and seeing the following issue.

failed to compute disapproval status: failed to get last disapprover: failed to load pull request data: non-200 OK status code: 403 Forbidden body: \"{\\n  \\\"documentation_url\\\": \\\"https://developer.github.com/v3/#abuse-rate-limits\\\",\\n  \\\"message\\\": \\\"You have triggered an abuse detection mechanism. Please wait a few minutes before you try again.\\\"\\n}\\n\"\ngithub.com/palantir/policy-bot/pull.(*GitHubContext).loadPagedData\n\t/home/runner/work/policy-bot/policy-bot/pull/github.go:735\ngithub.com/palantir/policy-bot/pull.(*GitHubContext).Comments\n\t/home/runner/work/policy-bot/policy-bot/pull/github.go:297\ngithub.com/palantir/policy-bot/policy/common.(*Methods).Candidates\n\t/home/runner/work/policy-bot/policy-bot/policy/common/methods.go:57\ngithub.com/palantir/policy-bot/policy/disapproval.(*Policy).lastActor\

I wonder if we should slow down some of the graphql queries to better abide by the abuse limits enforced by GH? At least when this occurs, it appears to hit repos that are in the same org, rather than it being a global problem.

from policy-bot.