#31424: django.utils.log.AdminEmailHandler won't include stack trace when
django.server logs are propogated
-------------------------------+--------------------------------------
Reporter: Wesley Ellis | Owner: nobody
Type: Bug | Status: closed
Component: Uncategorized | Version: 3.0
Severity: Normal | Resolution: invalid
Keywords: | Triage Stage: Unreviewed
Has patch: 0 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 0 | UI/UX: 0
-------------------------------+--------------------------------------
Changes (by Carlton Gibson):
* status: new => closed
* resolution: => invalid
Comment:
Hi Wesley.
The `django.server` logger applies to the WSGI server infrastructure that
powers the development `runserver` command. This is essentially a socket
server, so when that logger adds `self.request` to the log record, it is
adding the socket, not a Django request object that you're expecting. (I'm
guessing this is why `django.server` does not propagate by default.) When
propagating up to the `django` logger, and hitting the `mail_admins`
handler, it's that that's logged.
The properly formatted report that is generated is coming from the
`django.request` logger, which is used **inside** the request handling
machinery (`django/core/handlers`) and which gets the, expected, Django
request object.
--
Ticket URL: <https://code.djangoproject.com/ticket/31424#comment:1>
Django <https://code.djangoproject.com/>
The Web framework for perfectionists with deadlines.
--
You received this message because you are subscribed to the Google Groups
"Django updates" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to [email protected].
To view this discussion on the web visit
https://groups.google.com/d/msgid/django-updates/070.1bacd301b18054837f505dc241211dc7%40djangoproject.com.
