You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
xo-cli utility does not handle broken pipe on output (write() returning EPIPE) gracefully, printing an error message with a stack trace to stderr.
Example:
$ xo-cli --list-objects type=VM | head
[
{
"type": "VM",
"addresses": {
"0/ipv4/0": "*******",
"0/ipv6/0": "*******"
},
"affinityHost": "09798493-856c-470b-81b6-1b46f30ed7f9",
"auto_poweron": true,
"bios_strings": {
node:events:491
throw er; // Unhandled 'error' event
^
Error: write EPIPE
at afterWriteDispatched (node:internal/stream_base_commons:160:15)
at writeGeneric (node:internal/stream_base_commons:151:3)
at Socket._writeGeneric (node:net:917:11)
at Socket._write (node:net:929:8)
at writeOrBuffer (node:internal/streams/writable:392:12)
at _write (node:internal/streams/writable:333:10)
at Writable.write (node:internal/streams/writable:337:10)
at Object.listObjects (file:///home/tydlitat/mama/ghe/ext/xen-orchestra/packages/xo-cli/index.mjs:414:14)
at async main (file:///home/tydlitat/mama/ghe/ext/xen-orchestra/packages/xo-cli/index.mjs:282:14)
Emitted 'error' event on Socket instance at:
at emitErrorNT (node:internal/streams/destroy:151:8)
at emitErrorCloseNT (node:internal/streams/destroy:116:3)
at process.processTicksAndRejections (node:internal/process/task_queues:82:21) {
errno: -32,
code: 'EPIPE',
syscall: 'write'
}
Node.js v18.12.1
To Reproduce
Steps to reproduce the behavior:
Pipe the output of xo-cli into any process that will close the pipe early.
Exaple as above: xo-cli --list-objects type=VM | head
Expected behavior
xo-cli terminating gracefully on broken pipe, with no error logged.
Screenshots
n/a
Environment (please provide the following information):
Node: 18.12.1
hypervisor: XCP-ng 8.2.1
Additional context
Reproduced on Fedora FC37.
The text was updated successfully, but these errors were encountered:
Are you using XOA or XO from the sources? sources
If XOA:
stable
vslatest
)If XO from the sources:
Describe the bug
xo-cli utility does not handle broken pipe on output (write() returning EPIPE) gracefully, printing an error message with a stack trace to stderr.
Example:
To Reproduce
Steps to reproduce the behavior:
Pipe the output of xo-cli into any process that will close the pipe early.
Exaple as above:
xo-cli --list-objects type=VM | head
Expected behavior
xo-cli terminating gracefully on broken pipe, with no error logged.
Screenshots
n/a
Environment (please provide the following information):
Additional context
Reproduced on Fedora FC37.
The text was updated successfully, but these errors were encountered: