fix: Filter out "load" errors from thumbnail error reporting - #1517
Conversation
|
Warning Rate limit exceeded
You’ve run out of usage credits. Purchase more in the billing tab. ⌛ How to resolve this issue?After the wait time has elapsed, a review can be triggered using the We recommend that you space out your commits to avoid hitting the rate limit. 🚦 How do rate limits work?CodeRabbit enforces hourly rate limits for each developer per organization. Our paid plans have higher rate limits than the trial, open-source and free plans. In all cases, we re-allow further reviews after a brief timeout. Please see our FAQ for further information. ✨ Finishing Touches🧪 Generate unit tests (beta)
Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out. Comment |
Our new thumbnail error reporting is filled with
loaderrors. When looking into them, I found that the thumbnails loaded fine in my browser. But digging it into more, I believe the root cause is that our thumbnails don't have aContent-Typeheader. This may cause thumbnails to silently fail in the background, or potentially in cases of scrapers/crawlers trying to "view" them.I've created two PRs on the
thumbnail-apiandthumbnailer-lambdarepos to fix this, by attaching a correctContent-Typeto our thumbnails:dpla/thumbnail-api#31
dpla/thumbnailer-lambda#12
In the meantime, this PR removes "load" errors from our logging to cut back on the noise. We may restore it if we want once the
Content-Typefixes are deployed.