Our previous implementation used to limit number of errors to maximum of 60 per minute. This (arbitrary) limit was meant to prevent overloading with error reports when an error happens in a loop.
This is a low priority for the webapp (for now we'll use the filter callback to reimplement it), but may be a good thing to have by default for all users.
Our previous implementation used to limit number of errors to maximum of 60 per minute. This (arbitrary) limit was meant to prevent overloading with error reports when an error happens in a loop.
For example if the app does:
we'd expect to get only 60 errors and drop the rest.