-
Notifications
You must be signed in to change notification settings - Fork 8.3k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Bump node to 16.11.1 #110684
Bump node to 16.11.1 #110684
Changes from 13 commits
e5e911b
8eb3b06
03a1d7c
fc7db5e
75d8c55
f17e743
693e729
a0bc1b5
ec91485
e1cba8d
d7b7dbb
2511efe
6707f49
c1889d3
f819075
8a9b6f7
78bd79e
b2f4eb5
d87568a
d78cdda
296d75c
f393e81
e859e4d
1a4665d
7c15cc0
3c7714c
1db9c01
f7d4173
File filter
Filter by extension
Conversations
Jump to
Diff view
Diff view
There are no files selected for viewing
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -1 +1 @@ | ||
14.17.6 | ||
16.10.0 |
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -1 +1 @@ | ||
14.17.6 | ||
16.10.0 |
Original file line number | Diff line number | Diff line change |
---|---|---|
|
@@ -17,7 +17,7 @@ const kibanaVersion = Env.createDefault(REPO_ROOT, getEnvOptions()).packageInfo. | |
const savedObjectIndex = `.kibana_${kibanaVersion}_001`; | ||
|
||
describe('uiSettings/routes', function () { | ||
jest.setTimeout(120_000); | ||
jest.setTimeout(240_000); | ||
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. Is it necessary? There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. @jbudz do you remember? There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. I reverted it with 296d75c. It was timing out occasionally, but it was earlier in the pull request and on jenkins resources. |
||
|
||
beforeAll(startServers); | ||
/* eslint-disable jest/valid-describe */ | ||
|
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
As detailed in nodejs/node#38924 there's a v16 regression that wasn't documented. From v16
IncomingMessage
'close'
event means the request stream was ended not the underlying socket. This meant that the close event would fire before we even got to send the response.It's possible to listen to the
'close'
event on the socket itself withrequest.raw.req.socket
but the'close'
event on the response already captures both scenarios we care about: the response was sent or the socket terminated