-
-
Notifications
You must be signed in to change notification settings - Fork 305
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
FormatException: FormatException: Unexpected character (at character 1) #5554
Comments
Looks like /// Exception when the server returns "Too many requests".
class TooManyRequestsException implements Exception {
const TooManyRequestsException();
/// Start of the response body when the server received too many requests.
static const String _tooManyRequestsError =
'<!DOCTYPE html><html><head><meta name="robots" content="noindex"></head><body><h1>TOO MANY REQUESTS</h1>';
// ... That is, we'll still get the error as we're sending too many requests to the server, but the error will look cleaner. That's a start. For the record, the limits are:
Typical use case where we send many requests: the user page and its counts (products created/edited/...), which use "search products" requests. Generally speaking, an audit about when and how often we run "search products" and "get product" requests would make sense. |
that's exactly what happened there to a core contributor. |
On that page there are 4 "search products" counts and 2 "prices" counts. The current limitations/issues are with the 4 "search products" counts:
Assuming that this would solve many of the "search products" limitation issues and that it would be good enough for the moment, this is what I suggest regarding the user counts:
@teolemon What do you think of that? |
@teolemon ping |
yes, this looks reasonable @monsieurtanuki . We can't fight with the rate limiter, and being blocked means being completely blocked. |
Sentry Issue: SMOOTHIE-400
The text was updated successfully, but these errors were encountered: