Closed Sispheor closed 3 years ago
I have also encountered this with DEBUG=True
I'm encountering this as well with DEBUG as True or False. My traceback is nearly identical to that in https://github.com/encode/django-rest-framework/issues/6120#issue-349106359:
Python==3.6.4 django==2.1.7 djangorestframework==3.9.2 django-rest-multiple-models==2.1.3 coreapi==2.3.3
Side note: The traceback's inclusion of context
for each exception makes it a very real performance hit.
I'm also getting this issue Django==2.1.5 djangorestframework==3.9.1 coreapi==2.3.3
Is there a minimal example to recreate the issue? In short, trying to determine if this this is specific to certain use, or if this is a general issue with the docs.
I'm also getting this issue Python==3.7.4 django==2.2.4 djangorestframework==3.10.2 coreapi==2.3.3
Closing as stale
Not sure if it's a cireapi or Django Rest framework bug. When setting DEBUG to False, I get this error when reaching the generated documentation page of my project.
Steps to reproduce
DEBUG
to FalseExpected behavior
The documentation page is reachable and no errors in logs.
Actual behavior
The Doc page is generated but a lot of errors appear in the log output. Full log