lp://staging/~toykeeper/wsgi-oops/show-bzip-errors
- Get this branch:
- bzr branch lp://staging/~toykeeper/wsgi-oops/show-bzip-errors
Branch merges
- Oops Tools development team: Pending requested
-
Diff: 60 lines (+24/-3)2 files modifiedcanonical/oops/serializer.py (+2/-3)
canonical/oops/utils.py (+22/-0)
Branch information
Recent revisions
- 61. By Selene ToyKeeper
-
Made the bz2 serializer include stdout/stderr in exceptions.
(implemented by adding subprocess functions similar to those in Python 2.7) - 60. By Selene ToyKeeper
-
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.
(merged manually because Tarmac seems to be ignoring the approved MP)
- 55. By James Henstridge
-
Make reporting of 404 errors optional, via an optional oops_on_404 parameter for OopsWare.
- 54. By Danny Tamez
-
Added optional keyword so meta information can be excluded from the oops report.
Fixed condition involving env var dump-oops and oops.wanted that was preventing
oops reports from being generated.
Branch metadata
- Branch format:
- Branch format 7
- Repository format:
- Bazaar repository format 2a (needs bzr 1.16 or later)
- Stacked on:
- lp://staging/wsgi-oops