lp:~james-w/python-timeline-django/start-end-request

Branch merges

Propose for merging

No branches dependent on this one.

Merged into lp:python-timeline-django at revision 20

Michael Nelson (community): Approve on 2013-09-03

Diff: 41 lines (+20/-1)

2 files modified

timeline_django/tests/test_wsgi.py (+19/-0)
timeline_django/wsgi.py (+1/-1)

api

Related source package recipes

No recipes using this branch. (?)

Create packaging recipe

Related snap packages

Related bugs

Bug #1220089: OverlappingActionError from timeline

High

Fix Released

Link a bug report

Related blueprints

21. By James Westby on 2013-09-03

Save the environ before sending the wsgi_request_started signal.

Code that listens to the wsgi_request_started signal may want to use the
environ, but instead of using the one passed to the signal, it may
call get_environ() to get the saved version. That has to be the
current request's environ, not any previous request, so save the environ
before triggering the signal.

20. By James Westby on 2013-08-26

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.

19. By James Westby on 2013-08-24

Add SECRET_KEY that is now required for tests.

18. By James Westby on 2013-08-24

Drop the model signal handlers.

They cause a lot of noise in the timeline, and slow down all requests,
for little benefit. The context they provide for db queries can
just as easily be inferred from the backtraces on the queries.

17. By James Westby on 2012-09-22

Fix the README formatting.

16. By James Westby on 2012-09-22

Post-release version bump.

15. By James Westby on 2012-09-22

Release 0.0.2.

14. By James Westby on 2012-09-22

Move to a wsgi-based capture of the timeline for non-request events.

Overhaul how the timeline object is found to permit capturing the
request_start event, handle situations where no timeline is available
at all and a few mild cleanups.

The middleware doesn't get invoked before request_start, so a timeline
was never captured, and things went downhill from there. By capturing
at the wsgi layer this is avoided.

13. By Robert Collins on 2012-09-15

[r=james-w],[bug=1050852] Provide the action name when raising in _post_action, to allow triangulation of the cause.

12. By James Westby on 2012-02-28

Post-release version bump.