API rate limit exceeded
See original GitHub issueI’m getting this error fairly consistently when using the action:
Run actions/setup-go@v1.0.2
with:
go-version: 1.10
##[error]API rate limit exceeded for 199.7.166.17. (But here's the good news: Authenticated requests get a higher rate limit. Check out the documentation for more details.)
##[error]Node run failed with exit code 1
Issue Analytics
- State:
- Created 4 years ago
- Reactions:10
- Comments:18 (4 by maintainers)
Top Results From Across the Web
API Rate Limits - Deep Security Automation Center
API call rates are measured as the number of API calls that Deep Security Manager receives within the last sixty seconds. When a...
Read more >How to handle API rate limits: Do your integrations work at ...
An API rate limit might enforce, say, 100 requests per minute. Once requests exceed that number, it generates an error message to alert...
Read more >GitHub Error: Rate Limit Exceeded - Coder Diaries
When GitHub throws "Rate Limit Exceeded" error, the cause is exceeding the number of requests allowed per hour. Find out how to solve...
Read more >Rate Limits - Graph API - Meta for Developers - Facebook
A rate limit is the number of API calls an app or user can make within a given time period. If this limit...
Read more >What Does "Rate Limit Exceeded" Mean on Twitter? - ITGeared
Rate limit exceeded error means that you have exceeded the number of API (Application user interface) calls each user is allowed for a...
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
Friendly ping @damccorm - any chance this could get attention soon? Actions can’t be used as CI for Go until this is fixed, since builds start failing after just a dozen or so builds. The golang.org approach suggested above should work, and there’s even a PR ready 😃
@kjk @mvdan @damccorm I’ve updated API call to use the golang-dl one. I didn’t know about this.