Closed timronan closed 5 years ago
This traceback truncation only appears to occur with Python 2. At least this was the case with Python 2.7.15 versus 3.6.7 running on Linux (Ubuntu 18.04). It is repeatable using the test case in #63 if using a version before the commit that fixed that issue.
Resolution: this truncation was caused because the Exception occurred in a nested try-catch block, so only the "outer" stack trace was show. This was because the exception was re-raised with "raise e", which only re-raises with the most "local" stack trace. Solution is to simply re-raise with "raise" so all details, even nested exception handling, flow to the place the exception is caught.
When working on issue #63 we found that ROVER's critical error logs truncate. We must get complete stack traces from critical errors so we can more readily find and fix bugs.
Example: Logged Stack Trace.
Actual Stack Trace: