#31672: debug error view shows no traceback if exc.__traceback__ is None for
innermost exception
-------------------------------------+-------------------------------------
Reporter: Chris Jerdonek | Owner: Hasan
Type: | Ramezani
Cleanup/optimization | Status: closed
Component: Error reporting | Version: master
Severity: Normal | Resolution: fixed
Keywords: | Triage Stage: Ready for
technical_500_response,traceback,chain| checkin
Has patch: 1 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 0 | UI/UX: 0
-------------------------------------+-------------------------------------
Comment (by Chris Jerdonek):
Thanks for fixing the issue!
I looked at the PR after this was merged and made a comment:
https://github.com/django/django/pull/13513#issuecomment-707355649
By the way, I didn't get another email about this ticket until after the
PR was merged and approved. I think it might be a good addition to your
process in general if you could CC the reporter on any PR or otherwise
notify them (maybe this could be done automatically) to ensure they also
have a chance to see it before it's merged. I know this isn't the first
time I didn't have a chance to see a fix for an issue I reported until
after it was merged. In many cases, the extra pair of eyes can help
because the original reporter may have insights the PR author doesn't have
since they spent the time finding and diagnosing it.
--
Ticket URL: <https://code.djangoproject.com/ticket/31672#comment:10>
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/067.ff52e7d0a675aca0b11498e90b931a78%40djangoproject.com.
