From: Connor Kuehl <ckuehl@redhat.com>
To: Kevin Wolf <kwolf@redhat.com>
Cc: armbru@redhat.com, qemu-devel@nongnu.org, qemu-block@nongnu.org,
mreitz@redhat.com
Subject: Re: [PATCH 0/2] Clarify error messages pertaining to 'node-name'
Date: Wed, 3 Mar 2021 07:48:49 -0600 [thread overview]
Message-ID: <5e7f48f6-0558-76a7-6e8d-a214d9d46fa5@redhat.com> (raw)
In-Reply-To: <20210303095320.GC5254@merkur.fritz.box>
On 3/3/21 3:53 AM, Kevin Wolf wrote:
> Am 02.03.2021 um 00:36 hat Connor Kuehl geschrieben:
>> Some error messages contain ambiguous representations of the 'node-name'
>> parameter. This can be particularly confusing when exchanging QMP
>> messages (C = client, S = server):
>>
>> C: {"execute": "block_resize", "arguments": { "device": "my_file", "size": 26843545600 }}
>> S: {"error": {"class": "GenericError", "desc": "Cannot find device=my_file nor node_name="}}
>> ^^^^^^^^^
>
> Arguably, this error message isn't great anyway because of the empty
> string node name. We didn't even look for a node name, so why mention it
> in the error message?
>
> But your patches are certainly a good improvement already. I would have
> merged them, but git grep 'nor node_name=' shows that you missed to
> update a few tests, so they fail after the series. I suppose you only
> caught the ones that are run by default in 'make check' and missed the
> ones that require running the qemu-iotests 'check' script manually.
Ah, good catch! Yes, I was only using `make check`, I'll use the `check`
script to uncover the other failures and fix them accordingly.
>> [..]
>
> This is a good explanation for the change you're making. I think it
> deserves being committed to the repository in the commit message for
> patch 1.
I'll move this to patch #1 in the next revision of this series.
Thank you!
Connor
prev parent reply other threads:[~2021-03-03 13:50 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-03-01 23:36 [PATCH 0/2] Clarify error messages pertaining to 'node-name' Connor Kuehl
2021-03-01 23:36 ` [PATCH 1/2] block: " Connor Kuehl
2021-03-01 23:36 ` [PATCH 2/2] blockdev: " Connor Kuehl
2021-03-03 9:53 ` [PATCH 0/2] " Kevin Wolf
2021-03-03 13:48 ` Connor Kuehl [this message]
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=5e7f48f6-0558-76a7-6e8d-a214d9d46fa5@redhat.com \
--to=ckuehl@redhat.com \
--cc=armbru@redhat.com \
--cc=kwolf@redhat.com \
--cc=mreitz@redhat.com \
--cc=qemu-block@nongnu.org \
--cc=qemu-devel@nongnu.org \
/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;
as well as URLs for NNTP newsgroup(s).