Author: pavlovic.sanja.91
Description:
Problem:
When I tried to dump database while the path to gzip executable was misconfigured, script didn’t exit immediately (since it cannot continue in a meaningful way), only printed the error and continued along, even though it could not do anything.
Explanation:
Looking into the current error handling, I saw it is set up to pass pass exceptions to python default exception handler. That is sufficient only when errors are non-fatal. But when fatal error occurs, if the script does not exit immediately, it starts spewing non-relevant error information and ultimately confuses the user.
Proposed solution:
Create another error handler (exception handler) for fatal errors, that would output the error message and exit the script on spot.
In the attachment is a simple implementation of error handler for fatal errors as well as fix for the issue described above on the spot where it was noticed.
Version: unspecified
Severity: enhancement