You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
It appears that github is being more aggressive about rate limiting, just happened in the past few weeks, but now to get a run to pass, I often have to rerun failed jobs several times for my cores.
The error output ends with this, which implies that there is a way to make an authenticated request. I see nothing in the documentation of compile-sketches that suggests that this is supported. It should be, because github seems to be trying to force people to authenticate actions (For quite a while I've occasionally had installation failures for the same reason, but those were few and far between and livewithable. It is no longer liverwithable. Every single attempt at running compile examples results in failures of this form, and it camoflages actual problems with the core.
The error ends in:
github.GithubException.RateLimitExceededException: 403 {"message": "API rate limit exceeded for 52.179.102.209. (But here's the good news: Authenticated requests get a higher rate limit. Check out the documentation for more details.)", "documentation_url": "https://docs.github.com/rest/overview/resources-in-the-rest-api#rate-limiting"}
Error: Process completed with exit code 1.
I would like the rate limit to not be reached. Either throttle the routines, or provide a mechanism and document it to use the "authenticated requests" that the error message mentions
'arduino/compile-sketches' version
arduino/compile-sketches@main
Additional context
it seems that they're moving in the direction of severely curtailing anyone who doesn't authenticate, (i imagine because they're seeing abuse), but with little fluency in yaml (i'm much better at AVR assembly than this newfangled stuff - my brain only has a 16-bit address space; that's why I never liked the ATmega2560) and with difficulty understanding how the hell the whole scheme is supposed to work I was unsuccessful at getting another much simpler CI script that wanted a token (I don't know if that's the same thing) what it wanted.
Describe the problem
It appears that github is being more aggressive about rate limiting, just happened in the past few weeks, but now to get a run to pass, I often have to rerun failed jobs several times for my cores.
The error output ends with this, which implies that there is a way to make an authenticated request. I see nothing in the documentation of compile-sketches that suggests that this is supported. It should be, because github seems to be trying to force people to authenticate actions (For quite a while I've occasionally had installation failures for the same reason, but those were few and far between and livewithable. It is no longer liverwithable. Every single attempt at running compile examples results in failures of this form, and it camoflages actual problems with the core.
The error ends in:
github.GithubException.RateLimitExceededException: 403 {"message": "API rate limit exceeded for 52.179.102.209. (But here's the good news: Authenticated requests get a higher rate limit. Check out the documentation for more details.)", "documentation_url": "https://docs.github.com/rest/overview/resources-in-the-rest-api#rate-limiting"}
Error: Process completed with exit code 1.
To reproduce
See the is example of a run that failed like this.
Expected behavior
I would like the rate limit to not be reached. Either throttle the routines, or provide a mechanism and document it to use the "authenticated requests" that the error message mentions
'arduino/compile-sketches' version
arduino/compile-sketches@main
Additional context
it seems that they're moving in the direction of severely curtailing anyone who doesn't authenticate, (i imagine because they're seeing abuse), but with little fluency in yaml (i'm much better at AVR assembly than this newfangled stuff - my brain only has a 16-bit address space; that's why I never liked the ATmega2560) and with difficulty understanding how the hell the whole scheme is supposed to work I was unsuccessful at getting another much simpler CI script that wanted a token (I don't know if that's the same thing) what it wanted.
Issue checklist
The text was updated successfully, but these errors were encountered: