Merge lp:~jtv/launchpad/bug-684669 into lp:launchpad
Proposed by
Jeroen T. Vermeulen
on 2010-12-03
| Status: | Merged | ||||
|---|---|---|---|---|---|
| Approved by: | Jeroen T. Vermeulen on 2010-12-03 | ||||
| Approved revision: | no longer in the source branch. | ||||
| Merged at revision: | 12049 | ||||
| Proposed branch: | lp:~jtv/launchpad/bug-684669 | ||||
| Merge into: | lp:launchpad | ||||
| Diff against target: |
99 lines (+11/-9) 5 files modified
lib/canonical/launchpad/webapp/adapter.py (+6/-0) lib/lp/soyuz/doc/archive-override-check.txt (+1/-1) lib/lp/soyuz/doc/soyuz-upload.txt (+1/-1) lib/lp/translations/doc/poexport-request.txt (+1/-1) lib/lp/translations/scripts/tests/test_reupload_translations.py (+2/-6) |
||||
| To merge this branch: | bzr merge lp:~jtv/launchpad/bug-684669 | ||||
| Related bugs: |
|
| Reviewer | Review Type | Date Requested | Status |
|---|---|---|---|
| Stuart Bishop | code | 2010-12-03 | Approve on 2010-12-04 |
| Brad Crittenden (community) | code | Approve on 2010-12-03 | |
|
Review via email:
|
|||
Commit Message
[r=bac,
Description of the Change
= Bug 684669 =
When we have problems with scripts, we keep running into the same questions: what store(s) are we connected to? As what database user? What database backend processes are connected to our process?
In this branch I add a bit of logging when connecting to the main database. It provides all this information, as well as the isolation level.
The extra information is logged at DEBUG2, so add lots of -v.
Jeroen
To post a comment you must log in.
review:
Approve
(code)
| Brad Crittenden (bac) wrote : | # |
Please clean up the commit message before landing. It looks like the code creating the message doesn't handle multiple reviewers very well.

You can now do 'logging. debug2( msg, args)' and avoid the import.
I didn't realize we could drop the test_suite() now. Cool!