wsgi-oops

lp:~toykeeper/wsgi-oops/stop-eating-errors

Created by Selene ToyKeeper on 2011-08-10 and last modified on 2011-08-10

Only Selene ToyKeeper can upload to this branch. If you are Selene ToyKeeper please log in for upload directions.

No branches dependent on this one.

Merged into lp:wsgi-oops at revision 60

Selene ToyKeeper (community): Approve on 2011-08-15

Tim Cole (community): Approve on 2011-08-10

Ricardo Kirkner (community): Needs Information on 2011-08-10

61. By Selene ToyKeeper on 2011-08-10: Removed test for previous change. It didn't work anyway.
(the test still passed even after the thing it tested was removed)
60. By Selene ToyKeeper on 2011-08-08: Make the file serializer *not* catch errors. Those are caught and logged by the calling code.
The change reverted here (from r43) seems to just eat errors, not log them.
So, when we had app errors, there was an error logging the error.
And an error logging the error which caused the logging error.
(still need to update unit tests accordingly)
59. By Tim Cole on 2011-05-10: Expose the thread-local setting for non-wsgi oopses.
58. By Tim Cole on 2011-05-10: Introduce a generic OOPS API not tied to WSGI.
57. By Anthony Lenton on 2011-04-25: Merged in lp:~elachuni/wsgi-oops/python2.7
56. By Tim Cole on 2011-03-05: Fix issue where all app errors are reported as oops dump errors.
55. By James Henstridge on 2011-02-01: Make reporting of 404 errors optional, via an optional oops_on_404 parameter for OopsWare.
54. By Danny Tamez on 2011-01-06: 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.
53. By Tim Cole on 2010-12-21: Add hooks for request completion tracking.
52. By Tim Cole on 2010-07-09: Properly handle closing of the result generator

This branch contains Public information

Everyone can see this information.