qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Eduardo Habkost <ehabkost@redhat.com>
To: Markus Armbruster <armbru@redhat.com>
Cc: Amador Pahim <apahim@redhat.com>,
	qemu-devel@nongnu.org, kwolf@redhat.com, ldoktor@redhat.com,
	famz@redhat.com, stefanha@gmail.com, mreitz@redhat.com,
	crosa@redhat.com
Subject: Re: [Qemu-devel] [PATCH v6 3/7] qemu.py: use python logging system
Date: Tue, 15 Aug 2017 16:58:27 -0300	[thread overview]
Message-ID: <20170815195827.GW3108@localhost.localdomain> (raw)
In-Reply-To: <87zib1s13v.fsf@dusky.pond.sub.org>

On Tue, Aug 15, 2017 at 10:10:12AM +0200, Markus Armbruster wrote:
> Please spell "Python" with a capital "P" (it's a proper name).
> 
> Amador Pahim <apahim@redhat.com> writes:
> 
> > Let's provide extra control and flexibility by using python logging
> > system instead of print and/or sys.std*.write().
> >
> > Signed-off-by: Amador Pahim <apahim@redhat.com>
> 
> How exactly does this change error messages?
> 
> Is logging the right tool to report errors to the human user?  I'm
> asking because logging and error reporting are generally separate
> things.  Example: a program runs into a recoverable error.  It logs the
> error, but does not report it.
> 
> Is reporting errors to stderr the right thing to do for library class
> QEMUMachine?  I doubt it.  Libraries throw exceptions and let their
> users decide how to handle them.

I believe the "qemu received signal" event is supposed to be
logged, not necessarily reported.  Callers can then choose where
the log messages should go (scripts could choose to send them
directly to stderr if verbose or debugging mode is enabled).  We
don't even need an exception for it: we can let callers check
exitcode() and decide what to do about the QEMU exit code.

The send_fd_scm() messages, on the other hand, could become
exceptions, and don't need the logging system at all.

-- 
Eduardo

  reply	other threads:[~2017-08-15 19:58 UTC|newest]

Thread overview: 31+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-07-31  8:51 [Qemu-devel] [PATCH v6 0/7] scripts/qemu.py fixes and cleanups Amador Pahim
2017-07-31  8:51 ` [Qemu-devel] [PATCH v6 1/7] qemu.py: use poll() instead of 'returncode' Amador Pahim
2017-07-31 14:07   ` Eduardo Habkost
2017-07-31  8:51 ` [Qemu-devel] [PATCH v6 2/7] qemu.py: fix is_running() return before first launch() Amador Pahim
2017-08-01 10:09   ` Stefan Hajnoczi
2017-08-01 10:50     ` Eduardo Habkost
2017-08-01 12:56       ` Amador Pahim
2017-08-02 13:35         ` Stefan Hajnoczi
2017-07-31  8:51 ` [Qemu-devel] [PATCH v6 3/7] qemu.py: use python logging system Amador Pahim
2017-07-31 14:50   ` Eduardo Habkost
2017-07-31 15:05     ` Amador Pahim
2017-08-15  8:10   ` Markus Armbruster
2017-08-15 19:58     ` Eduardo Habkost [this message]
2017-08-16  6:17       ` Markus Armbruster
2017-08-18 12:24         ` Amador Pahim
2017-07-31  8:51 ` [Qemu-devel] [PATCH v6 4/7] qemu.py: improve message on negative exit code Amador Pahim
2017-08-15  8:26   ` Markus Armbruster
2017-08-18 12:24     ` Amador Pahim
2017-08-18 13:57       ` Markus Armbruster
2017-08-18 14:33         ` Amador Pahim
2017-07-31  8:51 ` [Qemu-devel] [PATCH v6 5/7] qemu.py: use os.path.null instead of /dev/null Amador Pahim
2017-08-01 10:11   ` Stefan Hajnoczi
2017-08-22  2:24   ` Philippe Mathieu-Daudé
2017-07-31  8:51 ` [Qemu-devel] [PATCH v6 6/7] qemu.py: cleanup and improve launch()/shutdown() Amador Pahim
2017-08-15  8:45   ` Markus Armbruster
2017-07-31  8:51 ` [Qemu-devel] [PATCH v6 7/7] qemu.py: include debug information on launch error Amador Pahim
2017-08-15  8:57   ` Markus Armbruster
2017-08-18 12:42     ` Amador Pahim
2017-08-18 14:01       ` Markus Armbruster
2017-08-18 14:49         ` Amador Pahim
2017-08-21  9:14           ` Markus Armbruster

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=20170815195827.GW3108@localhost.localdomain \
    --to=ehabkost@redhat.com \
    --cc=apahim@redhat.com \
    --cc=armbru@redhat.com \
    --cc=crosa@redhat.com \
    --cc=famz@redhat.com \
    --cc=kwolf@redhat.com \
    --cc=ldoktor@redhat.com \
    --cc=mreitz@redhat.com \
    --cc=qemu-devel@nongnu.org \
    --cc=stefanha@gmail.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;
as well as URLs for NNTP newsgroup(s).