From: "Daniel P. Berrange" <berrange@redhat.com>
To: Eric Blake <eblake@redhat.com>
Cc: Luiz Capitulino <lcapitulino@redhat.com>,
qemu-devel@nongnu.org, Markus Armbruster <armbru@redhat.com>
Subject: Re: [Qemu-devel] [PATCH] qmp-shell: fix pretty printing of JSON responses
Date: Tue, 23 Feb 2016 10:53:45 +0000 [thread overview]
Message-ID: <20160223105345.GD22780@redhat.com> (raw)
In-Reply-To: <56CB855B.1030906@redhat.com>
On Mon, Feb 22, 2016 at 03:02:03PM -0700, Eric Blake wrote:
> On 02/22/2016 10:02 AM, Daniel P. Berrange wrote:
> > Pretty printing of JSON responses is important to be able
> > to understand large responses from query commands in
> > particular, eg
> >
> > (QEMU) query-chardev
> > { u'return': [ { u'filename': u'vc',
> > u'frontend-open': False,
> > u'label': u'parallel0'},
> > { u'filename': u'vc',
> > u'frontend-open': True,
> > u'label': u'serial0'},
> > { u'filename': u'unix:/tmp/qemp,server',
> > u'frontend-open': True,
> > u'label': u'compat_monitor0'}]}
> >
> > Unfortunately this was broken during the addition of
> > the verbose flag in
> >
> > commit 1ceca07e48ead0dd2e41576c81d40e6a91cafefd
> > Author: John Snow <jsnow@redhat.com>
> > Date: Wed Apr 29 15:14:04 2015 -0400
> >
> > scripts: qmp-shell: Add verbose flag
> >
> > This is because that change turned the python data
> > structure into a formatted JSON string before the
> > pretty print was given it. So we're just pretty
> > printing a string, which is a no-op.
> >
> > This fixes pretty printing of the command responses
> > and as an added benefit it will also pretty print
> > command arguments in verbose mode
> >
> > (QEMU) object-add qom-type=secret id=sec0 props={"data":"123456"}
> > { 'arguments': { 'id': 'sec0',
> > 'props': { u'data': u'123456'},
> > 'qom-type': 'secret'},
> > 'execute': 'object-add'}
> > { u'return': { }}
>
> That's an odd mix of regular and Unicode strings. Any ideas why it is
> happening? But the patch is a strict improvement, so:
It is todo with the way qmp-shell parses the command line. The qom-type
and id arguments it just parses directly, but the last props argument
it gets by using json.loads() which returns unicode strings.
I realized we can avoid this issue and improve output style by not
pretty printing a python data struture, and instead telling the json
formatter to pretty print its output. So I've sent a v2 that does that
Regards,
Daniel
--
|: http://berrange.com -o- http://www.flickr.com/photos/dberrange/ :|
|: http://libvirt.org -o- http://virt-manager.org :|
|: http://autobuild.org -o- http://search.cpan.org/~danberr/ :|
|: http://entangle-photo.org -o- http://live.gnome.org/gtk-vnc :|
prev parent reply other threads:[~2016-02-23 10:53 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-02-22 17:02 [Qemu-devel] [PATCH] qmp-shell: fix pretty printing of JSON responses Daniel P. Berrange
2016-02-22 22:02 ` Eric Blake
2016-02-23 10:53 ` Daniel P. Berrange [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=20160223105345.GD22780@redhat.com \
--to=berrange@redhat.com \
--cc=armbru@redhat.com \
--cc=eblake@redhat.com \
--cc=lcapitulino@redhat.com \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.