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

Report rate-limiting errors clearly #1440

Open
rauno56 opened this issue May 18, 2022 · 1 comment
Open

Report rate-limiting errors clearly #1440

rauno56 opened this issue May 18, 2022 · 1 comment
Labels
priority: p3 Desirable enhancement or fix. May not be included in next release. type: feature request ‘Nice-to-have’ improvement, new feature or different behavior or design.

Comments

@rauno56
Copy link

rauno56 commented May 18, 2022

Is your feature request related to a problem? Please describe.

I suspect our releases here, are erroring because of GH rate limiting, but we have no way to certainly tell - I suspect rate-limiting errors are just reported as Server Errors.

Describe the solution you'd like

A perfect solution would include

  1. warning about the rate-limit being close(GH has headers in the response to check for that),
  2. error messages to indicate whether it was because of rate-limiting or not and
  3. a way to avoid the rate-limiting by slowing the requests down or breaking the release up into parts.

Additional context

@rauno56 rauno56 added priority: p3 Desirable enhancement or fix. May not be included in next release. type: feature request ‘Nice-to-have’ improvement, new feature or different behavior or design. labels May 18, 2022
@dermidgen
Copy link

Bump; this would really be nice. Large repos with many open PRs hit rate limits pretty quickly.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
priority: p3 Desirable enhancement or fix. May not be included in next release. type: feature request ‘Nice-to-have’ improvement, new feature or different behavior or design.
Projects
None yet
Development

No branches or pull requests

2 participants