Markus Armbruster writes:
> I tried to include the amended patch in today's pull request, but
> observed "make check" hangs with it.
False alarm: I just got a hang on master. I intend to include this
patch in my next pull request. Sorry for the delay.
Markus Armbruster writes:
> Michal Privoznik writes:
>
>> On 9/13/19 2:52 PM, Markus Armbruster wrote:
>>> Michal Privoznik writes:
>>>
If a command is disabled an error is reported. But due to usage
of error_setg() the class of the error is GenericError which does
not help
Michal Privoznik writes:
> On 9/13/19 2:52 PM, Markus Armbruster wrote:
>> Michal Privoznik writes:
>>
>>> If a command is disabled an error is reported. But due to usage
>>> of error_setg() the class of the error is GenericError which does
>>> not help callers in distinguishing this case from
On 9/13/19 2:52 PM, Markus Armbruster wrote:
Michal Privoznik writes:
If a command is disabled an error is reported. But due to usage
of error_setg() the class of the error is GenericError which does
not help callers in distinguishing this case from a case where a
qmp command fails regularly
Michal Privoznik writes:
> If a command is disabled an error is reported. But due to usage
> of error_setg() the class of the error is GenericError which does
> not help callers in distinguishing this case from a case where a
> qmp command fails regularly due to other reasons. Use
>
On 8/30/19 8:29 AM, Michal Privoznik wrote:
> If a command is disabled an error is reported. But due to usage
> of error_setg() the class of the error is GenericError which does
> not help callers in distinguishing this case from a case where a
> qmp command fails regularly due to other reasons.
If a command is disabled an error is reported. But due to usage
of error_setg() the class of the error is GenericError which does
not help callers in distinguishing this case from a case where a
qmp command fails regularly due to other reasons. Use
CommandNotFound error class which is much closer
