-
Notifications
You must be signed in to change notification settings - Fork 370
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
Actions fails if rate Limit is not enabled #1156
Comments
Hello @ggabijaa |
When I check the documentation - https://docs.github.com/en/[email protected]/admin/configuring-settings/configuring-user-applications-for-your-enterprise/configuring-rate-limits#about-rate-limits-for-github-actions - I can see, that it says:
Not having a rate limit is expected state and it should not be logged as an error - https://github.com/actions/stale/blob/main/src/classes/issues-processor.ts#L648 What do you think? |
Is this still being analyzed? At least a flag to not check for rate limites could be considered, or just remove this error print for GH Enterprise instances. Thank you. |
Hi @ggabijaa , We tried to investigate the issue with the provided details on a self hosted runner and we see that the workflow seems to work fine without any rate limit issue. It will really helpful if you could share a link to a public repository to help us with further investigation on the issue. |
Hi @ggabijaa , We are awaiting for your response, you can let us know if you have any queriers or the issue still exists. |
hello, yes workflow does work and is marked as successful, however error is printed. I cant send you the link of the repository, as its enterprise. Action works as expected in public Github. Attaching logs for the workflow run in enterprise:
|
Description:
When running action on schedule errors due to rateLimit. The actions is marked as successful but logs were showing errors:
Is this expected behavior? Should action error out when rateLimit, not enabled?
Action version: V9
Platform: Rocky Linux
Runner type: Self-hosted
Workfkow config:
The text was updated successfully, but these errors were encountered: