Currently when using grpc-node, any gRPC errors get raised with somewhat unhelpful stack traces (see #1250, #1661, #1808 for some examples):
Error: 14 UNAVAILABLE: Stream refused by server
at Object.callErrorFromStatus (/usr/src/app/node_modules/@grpc/grpc-js/build/src/call.js:31:26)
at Object.onReceiveStatus (/usr/src/app/node_modules/@grpc/grpc-js/build/src/client.js:176:52)
at Object.onReceiveStatus (/usr/src/app/node_modules/@grpc/grpc-js/build/src/client-interceptors.js:336:141)
at Object.onReceiveStatus (/usr/src/app/node_modules/@grpc/grpc-js/build/src/client-interceptors.js:299:181)
at /usr/src/app/node_modules/@grpc/grpc-js/build/src/call-stream.js:145:78
at processTicksAndRejections (internal/process/task_queues.js:75:11)
The original trace is lost and this makes debugging the source of any errors more difficult. Can we splat on the original stack trace onto any thrown errors?
Currently when using grpc-node, any gRPC errors get raised with somewhat unhelpful stack traces (see #1250, #1661, #1808 for some examples):
The original trace is lost and this makes debugging the source of any errors more difficult. Can we splat on the original stack trace onto any thrown errors?