Merge lp:~toykeeper/wsgi-oops/stop-eating-errors into lp:wsgi-oops
Status: | Merged |
---|---|
Approved by: | Selene ToyKeeper |
Approved revision: | 61 |
Merged at revision: | 60 |
Proposed branch: | lp:~toykeeper/wsgi-oops/stop-eating-errors |
Merge into: | lp:wsgi-oops |
Diff against target: |
69 lines (+6/-28) 2 files modified
canonical/oops/serializer.py (+6/-10) canonical/oops/tests/test_serializer.py (+0/-18) |
To merge this branch: | bzr merge lp:~toykeeper/wsgi-oops/stop-eating-errors |
Related bugs: |
Reviewer | Review Type | Date Requested | Status |
---|---|---|---|
Selene ToyKeeper (community) | Approve | ||
Tim Cole (community) | Approve | ||
Ricardo Kirkner (community) | Needs Information | ||
Review via email: mp+71014@code.launchpad.net |
Commit message
Fixed an error in the error logger for the error logger. Oh, metabugs, how do I love thee?
ISD keeps getting blank OOPS reports. It turns out there is an error in the error logger. Wsgi-oops has a failsafe to log that sort of thing, but unfortunately it has a bug too, which results in more blank errors. So, there is an error in the error logger for the error logger. It's kind of a metabug.
This fixes the outer most layer, so the outer errors will show up in the failsafe log. Once this is deployed, I can find out what the original error logger issue is, and fix that. Then after deploying that, I can hopefully find out what the original app errors are.
I basically reverted parts of revno: 43 by natalia.bidart. It seems not to have the desired effect (the code worked only 2 times out of 70615 errors in my log), and even the test for the feature didn't work. It still passed after removing the feature it was supposed to test.
Description of the change
ISD keeps getting blank OOPS reports. It turns out there is an error in the error logger. Wsgi-oops has a failsafe to log that sort of thing, but unfortunately it has a bug too, which results in more blank errors. So, there is an error in the error logger for the error logger. It's kind of a metabug.
This fixes the outer most layer, so the outer errors will show up in the failsafe log. Once this is deployed, I can find out what the original error logger issue is, and fix that. Then after deploying that, I can hopefully find out what the original app errors are.
I basically reverted parts of revno: 43 by natalia.bidart. It seems not to have the desired effect (the code worked only 2 times out of 70615 errors in my log), and even the test for the feature didn't work. It still passed after removing the feature it was supposed to test.
I'm a bit hesitant about this change. The original code doesn't *look* wrong at first sight. Since this is a shared codebase, I wouldn't want us to "fix" something and break other peoples expectations.
Can we have natalia involved in the review/discussion?