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

V8 Assertion error under node 10 #587

Closed
azz opened this issue May 4, 2018 · 6 comments
Closed

V8 Assertion error under node 10 #587

azz opened this issue May 4, 2018 · 6 comments

Comments

@azz
Copy link
Member

azz commented May 4, 2018

I got this interesting error when switching from a docker node:9 image to cypress/base:10 (which has node 10).

/usr/local/bin/node[1842]: ../src/node_contextify.cc:631:static void node::contextify::ContextifyScript::New(const v8::FunctionCallbackInfo<v8::Value>&): Assertion `args[1]->IsString()' failed.

 1: 
node::Abort() [/usr/local/bin/node]
 2: 
0x87b6c5 [/usr/local/bin/node]
 3: 
node::contextify::ContextifyScript::New(v8::FunctionCallbackInfo<v8::Value> const&) [/usr/local/bin/node]
 4: 
v8::internal::FunctionCallbackArguments::Call(v8::internal::CallHandlerInfo*) [/usr/local/bin/node]
 5: 
0xad5b9f [/usr/local/bin/node]
 6: 
v8::internal::Builtin_HandleApiCall(int, v8::internal::Object**, v8::internal::Isolate*) [/usr/local/bin/node]
 7: 0x26dee4e8427d
Error:  Error: Results passed to Danger JS did not include fails.

{}
    at /home/e40ccd31d1a3d9d9/node_modules/danger/distribution/dsl/DangerResults.js:20:19
    at Array.forEach (<anonymous>)
    at Object.validateResults (/home/e40ccd31d1a3d9d9/node_modules/danger/distribution/dsl/DangerResults.js:16:24)
    at Executor.<anonymous> (/home/e40ccd31d1a3d9d9/node_modules/danger/distribution/runner/Executor.js:161:41)
    at step (/home/e40ccd31d1a3d9d9/node_modules/danger/distribution/runner/Executor.js:32:23)
    at Object.next (/home/e40ccd31d1a3d9d9/node_modules/danger/distribution/runner/Executor.js:13:53)
    at /home/e40ccd31d1a3d9d9/node_modules/danger/distribution/runner/Executor.js:7:71
    at new Promise (<anonymous>)
    at __awaiter (/home/e40ccd31d1a3d9d9/node_modules/danger/distribution/runner/Executor.js:3:12)
    at Executor.handleResults (/home/e40ccd31d1a3d9d9/node_modules/danger/distribution/runner/Executor.js:157:16)

Not sure if it is actionable as it is probably difficult to reproduce, but I thought I'd raise it nonetheless.

@orta
Copy link
Member

orta commented May 4, 2018

I had another issue with node 10 here - #574 (comment)

Figured I would punt on it, might be worth putting it on CI now

@WOLVIE97
Copy link

WOLVIE97 commented May 7, 2018

Hmmmm🤔

@orta
Copy link
Member

orta commented Sep 21, 2018

I habe node 10 on CI now 👍

@orta orta closed this as completed Sep 21, 2018
@azz
Copy link
Member Author

azz commented Feb 6, 2019

Just went to upgrade our build from node 8 to 10, and I'm still seeing this error under node 10 and 11 docker containers 😢

Apparently it's due to code requiring node internals (process.binding('contextify')). Apparently installing natives as a dependency fixes the issue?

nodejs/node#20281

@orta
Copy link
Member

orta commented Feb 6, 2019

Adding it does? the danger-js codebase doesn't have natives as a dependency (happy to add it?)

@azz
Copy link
Member Author

azz commented Feb 6, 2019

I'm not really sure 😢 adding it to our root package didn't make a difference, when we added it to danger we got a different error.

I ran this in a fresh directory:

npm init -y
npm i danger
ag 'process.binding('

and didn't find anything requiring contextify so I'm not really sure what's causing this.

@orta
Copy link
Member

orta commented Feb 6, 2019

:-/ - I dunno man

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

No branches or pull requests

3 participants