-
Notifications
You must be signed in to change notification settings - Fork 1k
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
Stack overflow when using Django Debug Toolbar 1.8 (works fine in 1.7) #950
Comments
I can confirm the same problem when using DDT 1.8 with Django 1.8. |
I've seen the same issue--it was triggered for me when using a StreamField block that specified a template. Adding that template to the |
@gasman I thought you might want to have a look at this issue. |
Possibly related to wagtail/wagtail#2874...? |
I've experienced the same thing with DDT 1.8, Django 1.11.2 and Wagtail 1.10.1. After some investigation, there is an infinite loop created in panels.py:128, in Wagtail's case the |
I've monkey-patched it to get it working for those using Wagtail. The patch is here: I don't expect this should be a P.R., since it is Wagtail specific. |
Another hotfix for this is to exclude templates used by
And add to
From DDT doc for
Works for me. |
We had this issue with Django Debug Toolbar 1.8 and django-floppyforms and fixed this problem in a similar way:
We also decided to disable the TemplatesPanel by default because it was slowing the page heavily. Page loads were three times as slow in comparison with Django Debug Toolbar 1.7. |
This issue is outlined in django-commons/django-debug-toolbar#950 and seems to crop up when one has debug toolbar enabled and attempts to add an incident.
This issue is outlined in django-commons/django-debug-toolbar#950 and seems to crop up when one has debug toolbar enabled and attempts to add an incident.
there's a structblock template or two in there django-commons/django-debug-toolbar#950
This is liable to cause infinite loops on debug / logging code that attempts to log the fact that it's rendered a template with this value in the context. Fixes wagtail#2874, django-commons/django-debug-toolbar#950
Fixed in wagtail/wagtail#3738 - I think this can be closed, as it's a Wagtail issue. |
Thanks @gasman! |
This is liable to cause infinite loops on debug / logging code that attempts to log the fact that it's rendered a template with this value in the context. Fixes #2874, django-commons/django-debug-toolbar#950
Also affects |
Good afternoon, I'm getting a stack overflow error when I try to use DJDT 1.8 on routes served by the Wagtail CMS. The same routes / pages work with DJDT 1.7. I'm running Django 1.11.2 and Wagtail 1.10.1. Here's the trace:
I'm fine with running 1.7 for now, but am at a loss with where to start digging into this issue. Any ideas, advice, or hopefully solutions? Thanks in advance.
The text was updated successfully, but these errors were encountered: