Paolo Bonzini <pbonz...@redhat.com> writes: > Il 17/10/2012 16:43, Markus Armbruster ha scritto: >>> > Error propagation is already there for socket backends, even though >>> > it is (and remains) incomplete because no Error is passed to the >>> > NonBlockingConnectHandler. >> Why is that a problem? > > It means that the exact error message still cannot be sent to the user > if the OS reports it asynchronously via SO_ERROR. If > NonBlockingConnectHandler received an Error**, we could for example > report the error class and/or message via a new field of the > query-migration command even if it is reported asynchronously.
First time you mention the problem in a commit message could use a variant of this explanation.
