Skip to content
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

docs: remove reference to Node 10 incompatibility #449

Merged
merged 3 commits into from
Jul 18, 2018

Conversation

watson
Copy link
Contributor

@watson watson commented Jul 17, 2018

The bug in V8 that meant we couldn't instrument Node 10 was fixed and Node 10.4.0 shipped with a newer version of V8.

This is the original bug report in Node: nodejs/node#20516
This is the PR that fixed it in Node: nodejs/node#19989

Closes #448

The bug in V8 that meant we couldn't instrument Node 10 was fixed and
Node 10.4.0 shipped with a newer version of V8.

This is the original bug report in Node:
nodejs/node#20516

This is the PR that fixed it in Node:
nodejs/node#19989

Closes elastic#448
@watson watson self-assigned this Jul 17, 2018
@watson watson requested a review from Qard July 17, 2018 09:34
@@ -13,9 +13,6 @@ var semver = require('semver')
// hapi 17+ requires Node.js 8.9.0 or higher
if (semver.lt(process.version, '8.9.0') && semver.gte(pkg.version, '17.0.0')) process.exit()

// hapi does not work on Node.js 10 because of https://github.com/nodejs/node/issues/20516
if (semver.gte(process.version, '10.0.0-rc')) process.exit()
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Rather than fully removing this, can we change it to a range to indicate that certain early versions of 10.x are broken?

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Good idea. Fixed

Qard
Qard previously approved these changes Jul 17, 2018
@Qard
Copy link
Contributor

Qard commented Jul 17, 2018

Looks like the tests are failing on 10.x. 🤔

@watson
Copy link
Contributor Author

watson commented Jul 18, 2018

I think it's "just" hapi behaving different under Node 10 for some reason. As far as I can see hapi is emitting some events now that it wasn't doing under Node 9 when running our tests. Those are caught as errors and that causes our tests to fail. At least that's what I get from looking at the first failure. The other failures might be different.

I will have to look into if this is expected behavior and if so update the tests to expect it. This can take a while unfortunately.

@Qard
Copy link
Contributor

Qard commented Jul 18, 2018

Do you want to perhaps just merge the docs change and split the test change out to another PR?

@codecov-io
Copy link

codecov-io commented Jul 18, 2018

Codecov Report

Merging #449 into master will decrease coverage by <.01%.
The diff coverage is n/a.

Impacted file tree graph

@@            Coverage Diff             @@
##           master     #449      +/-   ##
==========================================
- Coverage   82.27%   82.26%   -0.01%     
==========================================
  Files          42       42              
  Lines        2268     2267       -1     
==========================================
- Hits         1866     1865       -1     
  Misses        402      402
Impacted Files Coverage Δ
lib/agent.js 94.31% <0%> (-0.04%) ⬇️

Continue to review full report at Codecov.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update 1240fb5...8afe3d3. Read the comment docs.

@watson
Copy link
Contributor Author

watson commented Jul 18, 2018

I'll merge this even though Jenkins is acting up. It's unrelated.

@watson watson merged commit 588df54 into elastic:master Jul 18, 2018
@watson watson deleted the node10 branch July 18, 2018 20:12
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Status for Node 10 ?
3 participants