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.
Define a good policy for safely handling (and caching?) external resources such as namecheck.fontdata.com and the MS vendor ID list.
See original GitHub issuee.g. here: http://35.225.170.228/report/d77de85c-eaa2-4738-9df6-ffc4a96b573d
I just scaled the dashboard to check ~ 5000 fonts in ~ 10 minutes. That’s ~ 8 fonts per second. Most probably not a load acceptable for http://namecheck.fontdata.com. Now I feel bad, we had around 1600 workers send requests at the same time to that service. I also ran these collection wide checks multiple times over the last days, but I think the last one, once it was properly scaled, broke that service.
I won’t run the full collection test anymore unless we have a solution for this and other external requests.
Issue Analytics
- State:
- Created 6 years ago
- Comments:13 (5 by maintainers)
Top Results From Across the Web
Top Related Medium Post
Top Related StackOverflow Question
Troubleshoot Live Code
Top Related Reddit Thread
Top Related Hackernoon Post
Top Related Tweet
Top Related Dev.to Post
Top Related Hashnode Post
Yeah, we should probably have something like this
I think this test should only run when the font does not exist in our collection.