keeper command line client does not exit when run with no arguments
Bug #1676690 reported by
James Henstridge
This bug affects 1 person
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
keeper (Ubuntu) |
New
|
Undecided
|
Unassigned |
Bug Description
If I run the keeper command line client with no arguments, it prints a debug message and then sits sits hangs seemingly doing nothing:
$ /usr/lib/
[debug] More or none arguments (src/cli/
I assume the tool is intended to only be called with a sub-command as an argument, so in this case I would expect it to print an error and exit immediately.
To post a comment you must log in.