Open jasoncontrib opened 7 years ago
This is a known race in miniclient. Do you have any data loss? The -e interface will show this too, though evidently less often, if you spam it.
On Apr 12, 2017 7:00 PM, "Jason Gao" notifications@github.com wrote:
Intermittent errors occur when using pipes via the domain socket; some invocations of the pipe command over the domain socket, e.g. echo "hello" | minimega -pipe foo cause errors such as the following:
2017/04/12 17:50:57 ERROR command_socket.go:76: write unix /tmp/minimega/minimega->@: use of closed network connection 2017/04/12 17:50:58 ERROR command_socket.go:169: read unix /tmp/minimega/minimega->@: read: connection reset by peer 2017/04/12 17:50:58 ERROR command_socket.go:76: write unix /tmp/minimega/minimega->@: use of closed network connection
This does not occur when not using the domain socket, e.g. when executing pipe foo "hello" in the main minimega CLI, or when using the domain socket with a non-miniplumber command, e.g. minimega -e vm info
— You are receiving this because you are subscribed to this thread. Reply to this email directly, view it on GitHub https://github.com/sandia-minimega/minimega/issues/905, or mute the thread https://github.com/notifications/unsubscribe-auth/AElrVBgpcuEhP_DuqsmFAn03ql5GdQytks5rvXOWgaJpZM4M8JGY .
Intermittent errors occur when using pipes via the domain socket; some invocations of the pipe command over the domain socket, e.g.
echo "hello" | minimega -pipe foo
cause errors such as the following:This does not occur when not using the domain socket, e.g. when executing
pipe foo "hello"
in the main minimega CLI, or when using the domain socket with a non-miniplumber command, e.g.minimega -e vm info