From 9905d18651f6c518a194ccac0e0750faa306bd6d Mon Sep 17 00:00:00 2001
From: Stefano Buliani <stefano.buliani@gmail.com>
Date: Wed, 25 Mar 2020 08:25:10 -0700
Subject: [PATCH 1/2] fix: Bump travis Node versions to the latest LTS
 supported by Lambda (10 and 12)

---
 .travis.yml | 4 ++--
 1 file changed, 2 insertions(+), 2 deletions(-)

diff --git a/.travis.yml b/.travis.yml
index 17caaa2e..e5924f3a 100644
--- a/.travis.yml
+++ b/.travis.yml
@@ -1,8 +1,8 @@
 language: node_js
 
 node_js:
-  - 6
-  - 8
+  - 10
+  - 12
   # - node # runs tests against latest version of Node.js for future-proofing
 
 before_install:

From cab6cefd78e742b1e7a90e67f610fd0a6ef20dcd Mon Sep 17 00:00:00 2001
From: Stefano Buliani <stefano.buliani@gmail.com>
Date: Wed, 25 Mar 2020 11:10:44 -0700
Subject: [PATCH 2/2] fix: Disabled failing integration test

---
 __tests__/integration.js | 6 +++++-
 1 file changed, 5 insertions(+), 1 deletion(-)

diff --git a/__tests__/integration.js b/__tests__/integration.js
index 0434d534..4e629793 100644
--- a/__tests__/integration.js
+++ b/__tests__/integration.js
@@ -384,7 +384,11 @@ describe('integration tests', () => {
     })
   })
 
-  test('forwardConnectionErrorResponseToApiGateway', (done) => {
+  // [TODO] The behavior of Node in versions >10 has changed an the error is no longer thrown
+  // in this case to trigger the 502 response. The unit tests still check the correct
+  // structure of the 502 response and we'll need to find a new way to test an express
+  // failure
+  test.skip('forwardConnectionErrorResponseToApiGateway', (done) => {
     const succeed = response => {
       delete response.headers.date
       expect(response).toEqual({