grpc-js: Look for ECONNRESET errors by parsing error messages

grpc · May 6, 2021 · e8efa33 · e8efa33
1 parent d82b1a3
commit e8efa33
Show file tree

Hide file tree

Showing 2 changed files with 7 additions and 2 deletions.
diff --git a/packages/grpc-js/package.json b/packages/grpc-js/package.json
@@ -1,6 +1,6 @@
 {
   "name": "@grpc/grpc-js",
-  "version": "1.3.0",
+  "version": "1.3.1",
   "description": "gRPC Library for Node - pure JS implementation",
   "homepage": "https://grpc.io/",
   "repository": "https://github.com/grpc/grpc-node/tree/master/packages/grpc-js",

diff --git a/packages/grpc-js/src/call-stream.ts b/packages/grpc-js/src/call-stream.ts
@@ -589,7 +589,12 @@ export class Http2CallStream implements Call {
                  * "Internal server error" message. */
                 details = `Received RST_STREAM with code ${stream.rstCode} (Internal server error)`;
               } else {
-                if (this.internalError.errno === os.constants.errno.ECONNRESET) {
+                /* Parsing the error message is fragile, because it's not part
+                 * of the contract, but it's the only usable information we
+                 * know for sure is available at this point. The failure case
+                 * a user seeing the error message, and a different error code.
+                 */
+                if (this.internalError.message.includes('ECONNRESET')) {
                   code = Status.UNAVAILABLE;
                   details = this.internalError.message;
                 } else {