Thats bizarre - we have a test (test_failure_fallback) that checks that there are not.
> /home/robertc/source/launchpad/oops-twisted/working/oops_twisted/tests/test_log.py(126)test_failure_fallback() -> expected_event = { (Pdb) print expected_message Logged OOPS id 33: ValueError: exception message (Pdb) print type(expected_message), repr(expected_message) <type 'unicode'> u'Logged OOPS id 33: ValueError: exception message' (Pdb)
Are you able to reproduce at will ? If so, can you put a breakpoint in log.py where it creates event['message'] and have a poke at what is happening?
I'm inclined to suspect something ffffunky in twisted's failure object.
Thats bizarre - we have a test (test_failure_ fallback) that checks that there are not.
> /home/robertc/ source/ launchpad/oops-twisted/working/ oops_twisted/ tests/test_ log.py( 126)test_ failure_ fallback( ) message) , repr(expected_ message)
-> expected_event = {
(Pdb) print expected_message
Logged OOPS id 33: ValueError: exception message
(Pdb) print type(expected_
<type 'unicode'> u'Logged OOPS id 33: ValueError: exception message'
(Pdb)
Are you able to reproduce at will ? If so, can you put a breakpoint in log.py where it creates event['message'] and have a poke at what is happening?
I'm inclined to suspect something ffffunky in twisted's failure object.