Matthias Kestenholz

That's surprising! We should definitely add some Jinja2-only syntax to the `basic.jinja` template. I did some work here https://github.com/jazzband/django-debug-toolbar/pull/1882 but yeah, it seems that the tracking is broken. I wonder...

It happens to me as well, but only intermittently. Maybe reloading a few times, enabling and disabling the profiler panel using the checkbox and/or restarting the development server works when...

I wonder if it would be possible to add a counter variable which tracks the number of currently active profiling sessions; the profiler would only be activated when incrementing from...

I see a fuzzy translation at the first location:  No idea why the fuzzy translation wouldn't simply be ignored.

@tim-schilling Yes. I don't know why that would be a fatal error when the whole translation is marked as `fuzzy` though.

@leandrodesouzadev The automatically generated documentation for panels (https://django-debug-toolbar.readthedocs.io/en/latest/panels.html#debug_toolbar.panels.Panel) will contain a reference to your new `GetResponse` stub. The stub itself isn't documented however, so Sphinx doesn't know where `GetResponse` should...

I have started digging into tracking SQL statements for a bit and I'm unsure how to proceed. ORM queries are started inside a thread pool executor when using an ASGI...

Yes, that does not work right now -- the SQL would have to contain a JOIN but does not. There are other projects trying to add CTE support to Django...

This ia a bug; `TreeNode` could ship with a system check or something which would detect this situation and emit a `django.core.checks.Error`. Maybe the check could even be implemented on...

Not sure how that should work seeing as you're not forced to use models with newsletter_subscription at all?