Hi,
Does this code make sense to anyone else? Any ideas on why a 429 is being returned?
In various ways I am finding an ember_jquery-530b142 in the report that returns a 429 error.
AI-generated summary
The discussion revolves around the issue of an Ember jQuery 429 error. outofthebox initially shares screenshots of the error and asks if anyone can make sense of it and provide ideas on why a 429 error is being returned. Falco clarifies that the Discourse Ajax function uses jQuery under the hood, so rate limit errors will always involve jQuery.
outofthebox inquires about how to find the origin of the rate limit error, and Falco suggests using browser developer tools to identify the issue. outofthebox mentions that the error occurs when using the instance normally but is unsure where to look in the developer tools.
Further discussion between outofthebox and Falco reveals that both Firefox and Chrome can be used to identify the source of 429 errors in the Network and Console tabs.
Discourse Ajax function uses jQuery under the hood, so every rate limit error coming from the Discourse will have jQuery somewhere in the backtrace.
Ok. Is there a good way to go a step back and find the origin of the rate limit error?
Does it happens when.using your instance normally? If it does, browsers developer tools will show you exactly why.
Hi, it does, but I am not sure where to look within the developer tools. Evidently the screenshots above are of the wrong error screen to find the source of the 429 error.
@Falco, Is there a particular browser you use for debugging? And is there a specific window or tool you recommend for identifying the source of 429 errors? Many thanks in advance!
Both Firefox and Chrome will show 429 sources in Network and Console tabs.