Open ralienpp opened 6 years ago
Currently raven
logs internal errors to raven.errors
and afaik will not propagate to the Sentry handler, and in theory should handle all errors, but some sneak in anyways. :)
I have looked into the code in an attempt to update the library myself and address this problem. I am wondering why this is happening though, because there is a "catch-all" exception handler that wraps the send_sync
function: https://github.com/getsentry/raven-python/blob/master/raven/transport/threaded.py#L165
Is there a document that describes the architecture of the client, so I can get a better idea of what happens under the hood?
I ran into the following situation - the software crashed,
raven
rightfully stepped in and prepared a report to be sent toSentry
. However, the system where the client was running was experiencing Internet connectivity issues - thusraven
itself crashed.Is there a way to define a handler for these situations? Or otherwise configure
raven
to try later or just ignore it? I have not found any discussion of these aspects in the documentation.This is how I am using the software: