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: API rate limit exceeded #448

Closed
austince opened this issue Oct 12, 2022 · 11 comments
Closed

HttpError: API rate limit exceeded #448

austince opened this issue Oct 12, 2022 · 11 comments
Assignees
Labels
bug Something isn't working

Comments

@austince
Copy link

We're seeing consistent rate limit exceeded errors from this action in our reasonably (~50 runs a day), starting from just a few days ago. Is it possible 4.0.2 increased the load in some way?

Screen Shot 2022-10-10 at 16 20 24

@MaksimZhukov
Copy link
Contributor

Hello @austince !
Could you please provide us with a link to the public repository where the issue occurs for further investigation if you are still facing it?

@austince
Copy link
Author

austince commented Nov 2, 2022

Hey there, not a public repo, unfortunately. We've limited the workflow triggers to just when PRs are created, which seems to help, but may not be an acceptable solution for all projects.

on:
  pull_request_target:
    types: [ created ]

@MaksimZhukov MaksimZhukov added the bug Something isn't working label Dec 12, 2022
@infinisil
Copy link

I just ran into this for NixOS/nixpkgs#211832

@dusan-trickovic
Copy link
Contributor

Hello, @austince ! Thank you for reaching out! I apologize for the late response. If that's alright, I would like to ask you to provide me with some additional context regarding this problem.

First, if you could, please provide a more detailed description of what seems to be wrong. As for limiting triggers, that could definitely help take some load off of the server processing those requests - as long as it complies with the specific needs of you or your organization.

However, there is another suggestion that could make spotting the problem a bit easier:

  • Since your original repo isn't public, it could be very helpful if you could create some minimal public repository with a sample workflow that threw this error for you. That way, we can potentially spot where the issue is, identify its culprit and eventually come up with a viable solution.

Thank you very much for your patience and cooperation :)

@dusan-trickovic
Copy link
Contributor

Hello, @austince ! I just wanted to give you a gentle ping to see if there are any updates on your end? Thank you :)

@austince
Copy link
Author

austince commented Jun 6, 2023

Hi @dusan-trickovic, it has been too long -- no longer have the context here either, not using this anymore. Feel free to close

@infinisil
Copy link

@dusan-trickovic See the above open-source PR I linked, it happened there too. Here's a workflow run that failed because of this error: https://github.com/NixOS/nixpkgs/actions/runs/3971508163

@dusan-trickovic
Copy link
Contributor

Hello @infinisil ! Thank you for letting us know about it. I just wanted to ask if you are still experiencing this error? If so, could you provide us with a more recent action run (since the logs and contents of the one you attached have since expired and are no longer available for viewing)? Thank you again for your cooperation :)

@dusan-trickovic
Copy link
Contributor

Hi @infinisil ! Sorry, just giving you a gentle ping to see if there are any updates on your end? Thank you! :)

@infinisil
Copy link

I don't have a more recent action run right now, I'll let you know when I do. I'm pretty sure it was caused by just having too many changes and labels trying to be added, because the above-linked PR moves about ~12k files around 😅

@dusan-trickovic
Copy link
Contributor

@infinisil thank you! In that case, I'm going to close this issue. If the problem occurs again, please let us know and we will reopen this issue for further investigation.

As always, thank you for the cooperation :)

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

No branches or pull requests

5 participants
@austince @infinisil @MaksimZhukov @dusan-trickovic and others