critical: on error you need to exit with status code != 0

[cr1st1p]

Version: ?.?.?

Bug Description

I'm using this in a pipeline. Somehow I ended with a bad password. Script showed the error but pipeline continued.
Meaning that script did not exit with error code != 0.
I see that you catch exceptions, print it, and... just continue and do a return 0 :-/

Steps To Reproduce

Expected Behavior

I would expect script to return non zero error code on errors

Possible Solution

... Only if you have suggestions on a fix for the bug