-
Notifications
You must be signed in to change notification settings - Fork 8.2k
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
Upgrade to Node.js 20 #162696
Upgrade to Node.js 20 #162696
Conversation
Documentation preview: |
1b15ba9
to
4fd7bc4
Compare
ae29e67
to
3bd9e85
Compare
Prior to Node.js 19.0.0, calling close while an idle client was connected to a server would not actually close the server before the client disconnected. This behavior was modified in Node.js 19.0.0: nodejs/node#43522 This resulted in our mock server being closed before we expected and as a result, some of the tests in `cluster.test.js` would fail. This is because the 1 second timeout is lower than the exponential backoff logic in the `_autoRetry` function inside the `native_realm.js` file. To get around this issue, the timeout have simply been incresed to 5 seconds instead of 1. This is not pretty, but it gets the job done.
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.
Code-only review. Data Discovery esdsl.test.ts
change LGTM 👍
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.
@jbudz your changes look awesome! Thanks 💯
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.
ent-search changes LGTM
💛 Build succeeded, but was flaky
Failed CI StepsTest Failures
Metrics [docs]Canvas Sharable Runtime
History
To update your PR or re-run it, just comment with: cc @watson |
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.
Ops changes LGTM. Checked some deployments and ran locally.
💔 All backports failed
Manual backportTo create the backport manually run:
Questions ?Please refer to the Backport tool documentation and see the Github Action logs for details |
This was reverted with f51e6cd until prebuilds are sorted. Compile times are causing issues for contributors. |
This reverts commit 029b3ba.
This reverts commit f51e6cd.
Closes #173334 This is a reattempt of doing what was planned on #162696 after solving the bottlenecks we discovered previously. --------- Co-authored-by: Jonathan Budzenski <[email protected]>
Closes elastic#173334 This is a reattempt of doing what was planned on elastic#162696 after solving the bottlenecks we discovered previously. --------- Co-authored-by: Jonathan Budzenski <[email protected]> (cherry picked from commit c6f9d98)
jbudz edits:
mock-fs
is currently not working with synchronous fs methods. All of our uses ofmock-fs
were already wrapped in asynchronous methods and so promises were used in place in several areas.Changes
Platforms and toolchains
Node.js changes
Blockers