Tim Schilling
Tim Schilling
I suspect the issue is that `toolbar._store` is exceeding the `RESULTS_CACHE_SIZE` because the toolbar renders on almost every request. If the server is also processing static files and the toolbar...
@brettdh It's on the server side. You'd have to fork the toolbar and use that in your project. Alternatively, you can try downgrading to v2.2. Turns out the History Panel...
@brettdh @ZhengYuen A thing to keep in mind about the toolbar is it stores the requests in memory. If the toolbar's ajax request hits a process that does not have...
> again, though, it works just fine for the django admin UI; it fails in the DRF browsable API only. That's going to require some investigation, but if increasing the...
That would be great.
@brettdh Regarding the difference between the admin and the browseable API, is it possible that you're hitting the browseable API unauthenticated or it's not sending the cookie along that would...
That seems reasonable. Would you mind creating a PR? As an aside, you can improve your queries performance (and the toolbars) if you can adjust your `Sample` queryset such that...
@federicobond Yes, but before you dive into that, please try #1438 (you'll need to install from source) to see if that resolves your issue.
Ah, that's a good idea! If possible, it would be nice to add in a notice that it automatically made that decision for a specific query.
Unfortunately, no. @AgarwalPragy and @federicobond, do you know what the cutoff should be for determining a "large query" to use a non-prettified query?