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

HttpError: You have triggered an abuse detection mechanism. #14

Open
BrightRan opened this issue Sep 30, 2020 · 2 comments
Open

HttpError: You have triggered an abuse detection mechanism. #14

BrightRan opened this issue Sep 30, 2020 · 2 comments

Comments

@BrightRan
Copy link

BrightRan commented Sep 30, 2020

Associated GitHub Community ticket: https://github.community/t/abuse-detection-mechanism-prevent-running-test/134996

When using this action in the workflow, the action failed with the following error (see here):

Error: HttpError: You have triggered an abuse detection mechanism. Please wait a few minutes before you try again.

@lots0logs
Copy link
Owner

We use this action at the company I work for extensively. We have never encountered that error. I'm not sure how it could be caused by this action.

@johentsch
Copy link

johentsch commented Jul 27, 2021

We are getting the same error and resulting from it, the workflow fails with /home/runner/files_modified.json: No such file or directory. A possible source of the error was brought up in actions/runner-images#1703 where @maxim-lobanov wrote:

I believe it is an issue with third-party action that you use gh-action-get-changed-files. On the quick look, it does N requests to server on every push to your PR where N is number of commits in your PR:

return gh.repos.getCommit(args);
.
It means that for kaisun2000/helix#1, for every push, this action does 541 requests to server and I don't see any delays between them. I don't know the rate limits for GH system token but it looks like a huge number of requests

Edit: It's consistently happening for a PR with 200 commits, but for another one with 113 commits the error did not re-appear after clicking on "Re-run jobs".

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

No branches or pull requests

3 participants