Exceptions raised during argument parsing are unhandled #136
Labels
No Label
bug
data loss
design finalized
good first issue
new feature area
question / support
security
waiting for response
No Milestone
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies
No dependencies set.
Reference: borgmatic-collective/borgmatic#136
Loading…
Reference in New Issue
No description provided.
Delete Branch "%!s(<nil>)"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
When an intentional validation exception occurs during argument parsing, borgmatic unceremoniously dumps out a Python traceback to the console with the validation error. The expected behavior is instead to catch the exception and display a more user-friendly error message.
Example:
This is a regression introduced by the recent changes in #116 around configuration file error handling.
Fixed by explicitly handling these exceptions. Will be part of the next release.
Just released in borgmatic 1.2.15.