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

Potential to be affected by secondary rate limits #1

Closed
cicirello opened this issue Aug 5, 2021 · 0 comments · Fixed by #5
Closed

Potential to be affected by secondary rate limits #1

cicirello opened this issue Aug 5, 2021 · 0 comments · Fixed by #5
Assignees
Labels
bug Something isn't working

Comments

@cicirello
Copy link
Owner

Describe the bug
There is potential for the rate limit on the code search API to interact with some other GitHub secondary rate limits. This issue probably won't turn up under most normal use-cases of the action. It came up under development, when multiple push events triggered test cases multiple times within relatively short timespan.

To Reproduce
Steps to reproduce the behavior:

  1. Configure a workflow that monitors multiple actions.
  2. Run the workflow multiple times in succession.
  3. Observe the secondary rate limit error message.

Expected behavior
Decrease likelihood of hitting rate limit (perhaps by adding a delay between queries).

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

Successfully merging a pull request may close this issue.

1 participant