check --only extract broken #217
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#217
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?
What I'm trying to do and why
I don't have a concrete use case other than testing the new
check --only
feature. But one use case I could imagine is running the slow extract consistency check from an infrequent cron job, separate from the regular consistency checks.Steps to reproduce
Run the following:
Actual behavior
Expected behavior
Run the borgmatic "extract" consistency check instead of erroring.
Other notes / implementation ideas
I think what's going on here is the argument parsing is getting confusing, thinking that we're trying to invoke the separate "extract" sub-command.
Environment
borgmatic version: 1.3.16
borgmatic installation method:
pip install --user
as rootBorg version: 1.1.10
Python version: 3.7.4
operating system and version: Manjaro stable
Okay, this is fixed and released (borgmatic 1.3.17). Required a fair amount of refactoring of the argument parsing so that different subparsers don't try to consume each others arguments erroneously.. when the value consumed by one subparser (
extract
incheck --only extract
) happens to match the name of another subparser (extract
)!