-
Notifications
You must be signed in to change notification settings - Fork 506
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
Support for Node 12 #849
Comments
I tried with Node 12 and it seems Nan 2.13.2 works fine as is. The missing part in this repo seems to be only adding |
I am seeing these when trying to build sqlite3. Is this nan's fault?
|
One more:
|
At least for the second one it seems like sqlite is directly using v8 API |
@matoro Which version of sqlite3 are you using? Is the latest version of NAN in use? |
I just cloned https://github.com/mapbox/node-sqlite3 and built locally (windows) with success. There are quite some deprecation warnings because sqlite uses |
I have patched the package I am building to bump to the latest version of sqlite3 (4.0.6) which depends on:
Edit: I also had to bump natives to 1.1.6 which is an indirect dependency. Let me see if bumping nan to the latest fixes it. Edit 2: scratch that, that's from master. sqlite3 release 4.0.6 depends on |
ok, if I use 4.0.6 instead maser of sqlite3 I can see the same errors. Most likely TryGhost/node-sqlite3#1093 fixed the issues but no release was made yet. |
tiny-secp256k1 maintainer here, here are the errors I found in NaN when compiling on v12.
|
IIRC the IsNearDeath error is fixed in the latest nan release.
…On Fri., 26 Apr. 2019, 12:04 pm Jonathan Underwood, < ***@***.***> wrote:
tiny-secp256k1 maintainer here, here are the errors I found in NaN when
compiling on v12.
In file included from ../../nan/nan_new.h:189:0,
from ../../nan/nan.h:223,
from ../native/addon.cpp:4:
../../nan/nan_implementation_12_inl.h: In static member function ‘static Nan::imp::FactoryBase<v8::StringObject>::return_t Nan::imp::Factory<v8::StringObject>::New(v8::Local<v8::String>)’:
../../nan/nan_implementation_12_inl.h:356:37: error: no matching function for call to ‘v8::StringObject::New(v8::Local<v8::String>&)’
return v8::StringObject::New(value).As<v8::StringObject>();
../../nan/nan_implementation_12_inl.h:356:58: error: expected primary-expression before ‘>’ token
return v8::StringObject::New(value).As<v8::StringObject>();
^
../../nan/nan_implementation_12_inl.h:356:60: error: expected primary-expression before ‘)’ token
return v8::StringObject::New(value).As<v8::StringObject>();
../../nan/nan_object_wrap.h: In destructor ‘virtual Nan::ObjectWrap::~ObjectWrap()’:
../../nan/nan_object_wrap.h:24:25: error: ‘class Nan::Persistent<v8::Object>’ has no member named ‘IsNearDeath’
assert(persistent().IsNearDeath());
^
../../nan/nan_object_wrap.h: In static member function ‘static void Nan::ObjectWrap::WeakCallback(const v8::WeakCallbackInfo<Nan::ObjectWrap>&)’:
../../nan/nan_object_wrap.h:127:26: error: ‘class Nan::Persistent<v8::Object>’ has no member named ‘IsNearDeath’
assert(wrap->handle_.IsNearDeath());
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
<#849 (comment)>, or mute
the thread
<https://github.com/notifications/unsubscribe-auth/AAENSWEHT2OO7AWVBIMRBALPSJPJHANCNFSM4HH7URQA>
.
|
I have a similar issue as @matoro with node-rdkafka: Log:
Code: ...
v8::Local<v8::Value> parameter = Nan::Get(object, field).ToLocalChecked();
...
v8::Local<v8::String> val = parameter->ToString(); Any ideas on that case ? |
@lrecknagel Don't use v8 directly, use NAN or napi. |
Hi, EDIT: narrowed down this issue to outdated dependencies and possible flaky tests. |
@darkgl0w Warnings are not errors, a memory dump might be required to diagnose the segfault |
|
* Temporarily fix Travis CI builds `nvm install node` will install the latest node version, which is 12 as of writing. Because of a problem in the resolved node-sass version this makes the builds fail. To get green builds until a proper fix for node 12 is introduced we'll install node 10, which is a LTS release, while 11 will be EOL in June 2019. @rokumatsumoto is maybe working on a fix, but I think green builds, especially for third party PRs are an important intermediate step. #2077 sass/node-sass#2633 nodejs/nan#849 https://github.com/nodejs/Release * Lock RuboCop to a version that supports Ruby 2.2 RuboCop 0.69.0 dropped support for Ruby 2.2, making RuboCop fail when it was installed since it pointed to the git repo instead of a specific version. https://github.com/rubocop-hq/rubocop/blob/v0.69.0/CHANGELOG.md#changes * Allow failures with ruby-head These might – currently – not be related to Ruby itself, but to the fact that bundler 2.1.0.pre.1 was installed, which is as of writing not supported by webpacker (`~> 1.12` is used). But this is to get the CI builds green again.
I'm going to close this out because I have no reason to believe at this point that the most recent release doesn't build with Node.js v12.x. The linked issues are either about older nan releases or caused by using Node or V8 APIs directly. Case in point: @imrehg, that's not nan@2.13.2, going by the line numbers. |
../../nan/nan_object_wrap.h:127:26: error: ‘class Nan::Persistentv8::Object’ has no member named ‘IsNearDeath’ |
* Add support for node 12 See mapbox/node-cpp-skel#54 nodejs/nan#849 * updates * Only need this * Use compatible versions * use dockerfile * updates * caching * Run commands from docker * Fix cov report * Fixes * lowercase * re-add cov check * change back to yarn run
* Temporarily fix Travis CI builds `nvm install node` will install the latest node version, which is 12 as of writing. Because of a problem in the resolved node-sass version this makes the builds fail. To get green builds until a proper fix for node 12 is introduced we'll install node 10, which is a LTS release, while 11 will be EOL in June 2019. @rokumatsumoto is maybe working on a fix, but I think green builds, especially for third party PRs are an important intermediate step. rails/webpacker#2077 sass/node-sass#2633 nodejs/nan#849 https://github.com/nodejs/Release * Lock RuboCop to a version that supports Ruby 2.2 RuboCop 0.69.0 dropped support for Ruby 2.2, making RuboCop fail when it was installed since it pointed to the git repo instead of a specific version. https://github.com/rubocop-hq/rubocop/blob/v0.69.0/CHANGELOG.md#changes * Allow failures with ruby-head These might – currently – not be related to Ruby itself, but to the fact that bundler 2.1.0.pre.1 was installed, which is as of writing not supported by webpacker (`~> 1.12` is used). But this is to get the CI builds green again.
* Temporarily fix Travis CI builds `nvm install node` will install the latest node version, which is 12 as of writing. Because of a problem in the resolved node-sass version this makes the builds fail. To get green builds until a proper fix for node 12 is introduced we'll install node 10, which is a LTS release, while 11 will be EOL in June 2019. @rokumatsumoto is maybe working on a fix, but I think green builds, especially for third party PRs are an important intermediate step. rails/webpacker#2077 sass/node-sass#2633 nodejs/nan#849 https://github.com/nodejs/Release * Lock RuboCop to a version that supports Ruby 2.2 RuboCop 0.69.0 dropped support for Ruby 2.2, making RuboCop fail when it was installed since it pointed to the git repo instead of a specific version. https://github.com/rubocop-hq/rubocop/blob/v0.69.0/CHANGELOG.md#changes * Allow failures with ruby-head These might – currently – not be related to Ruby itself, but to the fact that bundler 2.1.0.pre.1 was installed, which is as of writing not supported by webpacker (`~> 1.12` is used). But this is to get the CI builds green again.
Simply opening this as a tracking issue we can subscribe to and link to in upstream issues.
The text was updated successfully, but these errors were encountered: