From: "Laurențiu Leahu-Vlăducu" <l.leahu-vladucu@proxmox.com>
To: Thomas Lamprecht <t.lamprecht@proxmox.com>,
Proxmox Backup Server development discussion
<pbs-devel@lists.proxmox.com>
Subject: Re: [pbs-devel] [PATCH proxmox] proxmox-router: Improve CLI text output when printing empty lists
Date: Fri, 24 Jan 2025 09:58:37 +0100 [thread overview]
Message-ID: <f704973f-1459-4475-9df6-a1d3c5875ba9@proxmox.com> (raw)
In-Reply-To: <ef84d69b-d7de-45e6-a62c-5e7999059bfe@proxmox.com>
On 24.01.25 09:26, Thomas Lamprecht wrote:
> Am 22.01.25 um 14:14 schrieb Laurențiu Leahu-Vlăducu:
>> CLI tools that use '--output-format text' and print empty lists now
>> show a 'No results' message. Previously, this was sometimes confusing
>> because nothing was printed.
>
> I get where you come from with this but "No result" might be interpreted
> as error-like message by some though?
I am open to suggestions about the error message :) I was also not 100%
sure what the best message could be (especially one that shouldn't sound
like an error). I would have preferred to have something more specific
(e.g. "No tape drives found", but since this is a general formatter, I
cannot do that (at least not without adding additional parameters, which
is not worth it for this use case, IMO).
> And not sure how popular such an approach is, most standard CLI tools
> do not print anything if the result is empty, e.g. `ls` on an emtpy dir
> also outputs nothing. Are there any user requests/feedback on this?
Not that I know. This was kind of my own request, because I wrote some
docs on PBS tape backups and thought: if the user never used tape
drives/changers and is unsure whether they have been detected correctly,
they might try "proxmox-tape drive scan" or "proxmox-tape changer scan"
(or "list"), and if nothing is found, there is no output. Now, if the
user knows what the output should look like (a table with
drives/changers), it may be obvious that an empty output means that
proxmox-tape found nothing. But if the user never used PBS or tapes
before, or if that happened a long time ago, it might be unclear why
there is no output. Thus showing no output for "proxmox-tape drive scan"
makes it unclear whether this is an error or just empty.
I agree with you that printing something like "No result" makes it
inconsistent with other CLI tools. On the other hand, at least when
talking about tape drives/changers that require drivers and hardware
detection, it's nice to have some further details on what is happening
"behind the scenes".
Another argument in favor of it is that using --output-format json or
json-pretty also shows an empty list [], making it clearer that it's not
an error.
Just some of my thoughts ;) I know that this is a general formatter and
not related to proxmox-tape, but I thought it could make sense in other
Proxmox CLI tools as well.
_______________________________________________
pbs-devel mailing list
pbs-devel@lists.proxmox.com
https://lists.proxmox.com/cgi-bin/mailman/listinfo/pbs-devel
next prev parent reply other threads:[~2025-01-24 8:58 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-01-22 13:14 Laurențiu Leahu-Vlăducu
2025-01-24 8:26 ` Thomas Lamprecht
2025-01-24 8:58 ` Laurențiu Leahu-Vlăducu [this message]
2025-01-24 9:13 ` Thomas Lamprecht
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=f704973f-1459-4475-9df6-a1d3c5875ba9@proxmox.com \
--to=l.leahu-vladucu@proxmox.com \
--cc=pbs-devel@lists.proxmox.com \
--cc=t.lamprecht@proxmox.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox