question-mark
Stuck on an issue?

Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.

And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.

How to build or test locally/offline, to avoid rate-limiting?

See original GitHub issue

Presently 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:closed
  • Created 6 years ago
  • Comments:6 (5 by maintainers)

github_iconTop GitHub Comments

4reactions
fsihcommented, Mar 5, 2018
  • If you’re making changes to only scratch-blocks, you may be able to test locally by opening scratch-blocks/tests/vertical_playground.html in a browser, which will do no compression.
  • If you’re making changes only outside scratch-blocks, you can ‘npm unlink scratch-blocks’ from scratch-gui, and gui will automatically use the latest stable version of scratch-blocks.
  • If you’re trying to test changes to gui or vm or other repos and blocks together, you are kind of out of luck. I have hacked around this limit by editing scratch-blocks/dist/vertical.js directly. When you eventually can compile, you have to move all of your changes out of there to the appropriate files, or they will get overwritten.
0reactions
towerofnixcommented, Apr 29, 2018

Although this is closed because the question was resolved - this is properly fixed in #1471 now 😃 🎉

Read more comments on GitHub >

github_iconTop 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 >

github_iconTop Related Medium Post

No results found

github_iconTop Related StackOverflow Question

No results found

github_iconTroubleshoot Live Code

Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free

github_iconTop Related Reddit Thread

No results found

github_iconTop Related Hackernoon Post

No results found

github_iconTop Related Tweet

No results found

github_iconTop Related Dev.to Post

No results found

github_iconTop Related Hashnode Post

No results found