search

lots0logs / gh-action-get-changed-files

GitHub Action that saves changed files as JSON for use by other actions.
MIT License
88 stars 38 forks source link

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

Open BrightRan opened 4 years ago

BrightRan commented 4 years ago

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 commented 4 years ago

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 commented 3 years ago

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/virtual-environments#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: https://github.com/lots0logs/gh-action-get-changed-files/blob/002a3dec1083f13f4e1853c5c1dc26526ac185bc/index.js#L29. 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".