Merge lp:~james-w/python-timeline-django/start-end-request into lp:python-timeline-django
Proposed by
James Westby
Status: | Merged | ||||
---|---|---|---|---|---|
Approved by: | Natalia Bidart | ||||
Approved revision: | 20 | ||||
Merged at revision: | 19 | ||||
Proposed branch: | lp:~james-w/python-timeline-django/start-end-request | ||||
Merge into: | lp:python-timeline-django | ||||
Diff against target: |
234 lines (+135/-3) 5 files modified
timeline_django/hooks.py (+14/-0) timeline_django/signals.py (+5/-0) timeline_django/tests/test_hooks.py (+69/-0) timeline_django/tests/test_wsgi.py (+37/-1) timeline_django/wsgi.py (+10/-2) |
||||
To merge this branch: | bzr merge lp:~james-w/python-timeline-django/start-end-request | ||||
Related bugs: |
|
Reviewer | Review Type | Date Requested | Status |
---|---|---|---|
Natalia Bidart (community) | Approve | ||
Review via email: mp+182128@code.launchpad.net |
Commit message
Add signals for the start of the wsgi request and start of the response.
The django signal for request-finished fires when the client has consumed
the response. However, when generating an oops it can be done before this
meaning that the timeline doesn't have a reference for an end point.
This defines a response-started signal that fires when start_response
is called in the wsgi stack, making it more likely that there will be
an end point in the timeline.
Description of the change
Hi,
This is best described by the commit message, but should get us oopses
that better reflect the duration of the request.
Thanks,
James
To post a comment you must log in.
Looks good!