Skip to content

"Error when getting rateLimit: Rate limiting is not enabled." #1227

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

Open
2 of 5 tasks
taliastocks opened this issue Mar 19, 2025 · 8 comments · May be fixed by #1241
Open
2 of 5 tasks

"Error when getting rateLimit: Rate limiting is not enabled." #1227

taliastocks opened this issue Mar 19, 2025 · 8 comments · May be fixed by #1241
Assignees
Labels
bug Something isn't working

Comments

@taliastocks
Copy link

Description:
When running on GitHub Enterprise Server, rate limiting is not enabled. The action reports two error annotations:

Error when getting rateLimit: Rate limiting is not enabled.

Action version:
9.1.0

Platform:

  • Ubuntu
  • macOS
  • Windows

Runner type:

  • Hosted
  • Self-hosted

Repro steps:
Run the action on a self-hosted runner connected to GitHub Enterprise Server, version 3.15.2.

Expected behavior:
No errors should be reported. Everything worked fine, and there are no relevant rate limits.

Actual behavior:
The action reports an error getting rateLimit because rate limiting is not enabled.

@taliastocks taliastocks added bug Something isn't working needs triage labels Mar 19, 2025
@gowridurgad
Copy link

Hi @taliastocks,
Thank you for creating this issue. We will investigate it and provide feedback as soon as we have some updates.

@suyashgaonkar suyashgaonkar self-assigned this Mar 24, 2025
@suyashgaonkar
Copy link
Contributor

Hi @taliastocks, This looks like duplicate of #1156 . You can refer to follwoing comment in that issue for the solution. Please feel free to reach out if not resolved, and share with us the PR and the workflow runs where you encountered this issue for further investigation

@taliastocks
Copy link
Author

Thanks - we increased the operations per run and there is no change. We're not using personal access tokens for this workflow, so I'm not sure how that would help.

I'm not sure how I would share the PR and workflow run with you from a GitHub Enterprise Server instance.....

@tnavarra
Copy link

Hi, we are also experiencing this exact issue on a self-hosted Ubuntu runner against Enterprise Server. Setting operations-per-run to 1000 had no impact.

@suyashgaonkar
Copy link
Contributor

Hi @taliastocks, Please consider referring to the following documentation link of the Github REST API which are used behind the scenes in actions/stale to understand more on the rate limit and tokens associated with it. We also have created a example file for your reference in which we have passed repo-token to trying to replicate the issue with the help of iterations to exceed the rate limit, and follwoing is its run.

@suyashgaonkar
Copy link
Contributor

Hi @taliastocks , We are waiting for your response on the following ticket.

@taliastocks
Copy link
Author

Hi @suyashgaonkar,

You have linked to the documentation for GitHub Cloud. However, as I mentioned in this ticket, I am using GitHub Enterprise Server. Here is the correct link to documentation on rate limits for GitHub Enterprise Server.

Rate limits are disabled by default for GitHub Enterprise Server. Contact your site administrator to confirm the rate limits for your instance.

The example you have created is not helpful, as again, it is running against GitHub Cloud. This bug report is for GitHub Enterprise Server.

taliastocks added a commit to taliastocks/stale that referenced this issue Apr 16, 2025
Fix actions#1227. GitHub Enterprise Server has no rate limits by default, and returns status 404 from the rate_limit endpoint.
@taliastocks taliastocks linked a pull request Apr 16, 2025 that will close this issue
2 tasks
@taliastocks
Copy link
Author

The following PR should fix the issue: #1241

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.

4 participants