Reading nonexistent file from command line produces complaint about DB type, not file existence error

[robertbruntz]

Running duc ui -d <file> on a non-existent file produces an error that sounds like the file contains an unsupported DB type, rather than reporting that the file doesn't exist.

$ cat /etc/redhat-release
Rocky Linux release 8.10 (Green Obsidian)
$ duc --version
duc version: 1.4.5
options: cairo x11 ui tokyocabinet
$ duc ui -d /etc/fstab   # file does exist, but does not contain a DB
Error opening: /etc/fstab - unsupported DB type unknown, compiled for tokyocabinet
Unknown error, contact the author
$ duc ui -d /etc/fstab2   # file does not exist at all
Error opening: /etc/fstab2 - unsupported DB type unknown, compiled for tokyocabinet
Database not found
$ ls /etc/fstab2
ls: cannot access '/etc/fstab2': No such file or directory

A much-more-helpful message would be something like the one from ls, above, so that the user can more easily spot a path or filename typo, etc., rather than thinking that the file exists but has become corrupted.

[l8gravely]

>>>> "robertbruntz" == robertbruntz ***@***.***> writes: #robertbruntz created an issue (zevv/duc#349) Running duc ui -d <file> on a non-existent file produces an error that sounds like the file contains an unsupported DB type, rather than reporting that the file doesn't exist. $ cat /etc/redhat-release Rocky Linux release 8.10 (Green Obsidian) $ duc --version duc version: 1.4.5 options: cairo x11 ui tokyocabinet $ duc ui -d /etc/fstab # file does exist, but does not contain a DB Error opening: /etc/fstab - unsupported DB type unknown, compiled for tokyocabinet Unknown error, contact the author $ duc ui -d /etc/fstab2 # file does not exist at all Error opening: /etc/fstab2 - unsupported DB type unknown, compiled for tokyocabinet Database not found $ ls /etc/fstab2 ls: cannot access '/etc/fstab2': No such file or directory A much-more-helpful message would be something like the one from ls, above, so that the user can more easily spot a path or filename typo, etc., rather than thinking that the file exists but has become corrupted.

I'd like to ask you to test out the v1.5.0-rc1 branch and see if I got the test to work better. I've run into this myself and was trying to come up with a way to properly detect when you try to open a non-supported DB type for your current build and give you a better message in there. John