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

[taliastocks]

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.

[v-gowridurgad]

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

[suyashgaonkar]

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]

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]

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]

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]

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

[taliastocks]

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]

The following PR should fix the issue: #1241

[suyashgaonkar]

Hi @taliastocks , The above shared example was to demonstrate the passing of PAT in the stale workflow as a workaround for the issue. PAT can be passed in a stale workflow irrespective of the type of github server used.
Following is the code snippet from example above that pass the PAT in action/stale.

 steps:
      - uses: actions/stale@v9
        with:
          repo-token: ${{ secrets.STALE_REPO_TOKEN }}

Please let us know if you have tried passing PAT in the workflow to overcome rate limit issue or tried enabling the rate limit the way given in the following documentation , and it would also be helpful if you could share the logs of the workflow run where you are seeing this issue for further investigation.

[suyashgaonkar]

Hi @taliastocks , we are waiting for your response.