Stuck on an issue?

Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.

And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.

V8 Assertion error under node 10

See original GitHub issue

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.

Issue Analytics

State:
Created 5 years ago
Comments:6 (6 by maintainers)

Top GitHub Comments

1reaction

ortacommented, Sep 21, 2018

I habe node 10 on CI now 👍

0reactions

ortacommented, Feb 6, 2019

😕 - I dunno man

Top Results From Across the Web

Debug build assertion failed in V8 for parallel/test-error-reporting

Testing out adding Debug builds to CI and I have some failures that need looking at that'll need someone cleverer than me.

Assert | Node.js v19.3.0 Documentation

The node:assert module provides a set of assertion functions for ... WARNING: This does not throw an AssertionError in legacy assertion mode! assert....

Upgrading to Node 10 causing error in webpack build

I've tried upgrading package versions, including webpack (which I migrated to v4 with WDS v3). I've found this issue which seems to have...

Errors | Node.js v18 API

AssertionError s are a special class of error that can be triggered when Node.js detects an exceptional logic violation that should never occur....

Node.js Assert module - GeeksforGeeks

The assert module provides a set of assertion functions for verifying invariants. If the condition is true it will output nothing else an ......