-
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
Why don't my asynchronous callbacks work? #12
Comments
oh, cause we have a bug in v8::Local<v8::Object> obj = v8::Object::New();
obj->Set(NanSymbol("callback"), fn);
NanAssignPersistent(v8::Object, handle, obj); But fetch it as: return NanPersistentToLocal(handle).As<v8::Function>(); But it should be, (as in v8::Local<v8::Function> callback = NanPersistentToLocal(handle)->Get(NanSymbol("callback")).As<v8::Function>(); My bad. I can't recall why I added |
fixed in current 0.2.0, try again. |
Hm, was I supposed to change anything other than NAN? Still not working after updating to new version.The end result is still the same, test reports 'callback not fired'. I've had a successful build with 0.11.4 when not using NAN. |
ok, try again with 0.2.0, it's the |
ooops, push didn't work, done now, working in your node-snappy. |
Works in 0.11, not in 0.10. But more tests do pass with 0.10 than previously. |
Never mind, removed a superfluous NanScope I had put locally in Init in binding.cc and now it seems to work. Upstream should pull it soon. |
Trying to adapt node-snappy for NAN, I cannot get the asynchronous callbacks to work. All asynchronous tests fail with 'Callback not called', where all synchronous tests pass. What am I doing wrong?
kkoopa/node-snappy@kesla:master...master
The text was updated successfully, but these errors were encountered: