Merge lp:~lifeless/python-oops-tools/timeline into lp:python-oops-tools
| Status: | Merged |
|---|---|
| Approved by: | Robert Collins on 2012-09-19 |
| Approved revision: | 46 |
| Merged at revision: | 43 |
| Proposed branch: | lp:~lifeless/python-oops-tools/timeline |
| Merge into: | lp:python-oops-tools |
| Diff against target: |
135 lines (+30/-3) 6 files modified
buildout-templates/bin/oopstools.wsgi.in (+14/-1) buildout-templates/src/oopstools/settings.py.in (+1/-0) buildout.cfg (+0/-1) setup.py (+4/-0) src/oopstools/NEWS.txt (+6/-0) versions.cfg (+5/-1) |
| To merge this branch: | bzr merge lp:~lifeless/python-oops-tools/timeline |
| Related bugs: |
| Reviewer | Review Type | Date Requested | Status |
|---|---|---|---|
| William Grant | code | 2012-09-19 | Approve on 2012-09-19 |
|
Review via email:
|
|||
Commit Message
Django 1.3.3, new djangorecipe, and start capturing SQL activity in OOPSes raised by oops-tools itself.
Description of the Change
Upgrade oops-tools infrastructure a bit, get latest django in the 1.3 series - 1.3.3, and then on top of that introduce timeline-django so we can capture the SQL calls being made when oops-tools itself has an issue.
This also provides a bit of a reference-use-case for using django-timeline.
We may find we need to implement tighter query filtering - I don't know whether the django-sso-auth stuff will be caught properly, so we may end up deploying, getting a couple of traces, and then disabling in prod.
- 44. By Robert Collins on 2012-09-19
-
Add missed timeline_django dep.
| Robert Collins (lifeless) wrote : | # |
So yeah, I can see that - however, we'll drill in and do some data gathering when we deploy and disable if problematic. From there, we can land a change if needed or not.
I'll add a NEWS entry and land.
- 45. By Robert Collins on 2012-09-19
-
Merge trunk.
- 46. By Robert Collins on 2012-09-19
-
NEWS entry.

I'm a little reluctant to switch SQL logging on by default, but otherwise fine