Describe the bug:
We are regularly seeing the following uncaught exception in our node app. All of our calls to the MilvusClient are awaited and wrapped in a try...catch block, so I guess something's being done internal to the lib that is allowing for the uncaught exception.
2023-06-19T16: 01: 33.637Z - uncaughtException - {
"stack": "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 console.value (node:internal/console/constructor:300:16)
at console.warn (node:internal/console/constructor:382:26)
at Object.error (/home/user/dev/proj/node/node_modules/@grpc/grpc-js/build/src/logging.js:24:17)",
"message": "write EPIPE",
"errno": -32,
"code": "EPIPE",
"syscall": "write"
}
Describe the bug: We are regularly seeing the following uncaught exception in our node app. All of our calls to the MilvusClient are
await
ed and wrapped in atry...catch
block, so I guess something's being done internal to the lib that is allowing for the uncaught exception.Milvus-node-sdk version: 2.2.17