How to build or test locally/offline, to avoid rate-limiting?
See original GitHub issuePresently I’m getting this error in my console when I run build.py
:
SERVER ERROR: blockly_compressed_vertical.js (for example)
Too many compiles performed recently. Try again later.
This is a bit annoying. Apparently the only solution is to wait an hour or so until I’m not rate-limited anymore. How can I build scratch-blocks locally, to avoid this?
Apologies if I missed anything in the documentation wiki.
Issue Analytics
- State:
- Created 6 years ago
- Comments:6 (5 by maintainers)
Top Results From Across the Web
Rate-limiting strategies and techniques - Google Cloud
The most common reason for rate limiting is to improve the availability of API-based services by avoiding resource starvation.
Read more >Rate limits - GitLab Docs
There is a rate limit for testing webhooks, which prevents abuse of the webhook functionality. The rate limit is 5 requests per minute...
Read more >Your client has been rate-limited - 1Password Community
I've been using the CLI 2.0 in a bunch of tests lately and I've run into being rate limited.
Read more >How to Stop Being Rate Limited: Best Practices for Making API ...
Merge engineer David Donnelly walks readers through the best practices and approaches for implementing a robust rate limit tracker.
Read more >Best practices for avoiding rate limiting | Zendesk Developer ...
If you make a lot of API requests in a short amount of time, you may bump into the API rate limit for...
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
Although this is closed because the question was resolved - this is properly fixed in #1471 now 😃 🎉