fix: retry API requests when receiving error code EAI_AGAIN

Kubernetes clusters can have timeout because of slow DNS lookup, and it makes some requests return the error code EAI_AGAIN. It should ignore this error and retry transmitting a request if it stills having remaining retries.
snyk · Apr 28, 2020 · de32f36 · de32f36
1 parent e89c778
commit de32f36
Show file tree

Hide file tree

Showing 2 changed files with 12 additions and 0 deletions.
diff --git a/src/transmitter/index.ts b/src/transmitter/index.ts
@@ -122,5 +122,9 @@ function shouldRetryRequest(err: IRequestError, stillHaveRetries: boolean): bool
     return true;
   }
 
+  if (err.code === 'EAI_AGAIN') {
+    return true;
+  }
+
   return false;
 }
diff --git a/test/system/kind.test.ts b/test/system/kind.test.ts
@@ -103,6 +103,14 @@ tap.test('Kubernetes-Monitor with KinD', async (t) => {
       message: 'socket hang up',
     });
 
+  nock('https://kubernetes-upstream.snyk.io')
+    .post('/api/v1/dependency-graph')
+    .times(1)
+    .replyWithError({
+      code: 'EAI_AGAIN',
+      message: 'getaddrinfo EAI_AGAIN kubernetes-upstream.snyk.io',
+    });
+
   nock('https://kubernetes-upstream.snyk.io')
     .post('/api/v1/dependency-graph')
     .times(1)