-
Notifications
You must be signed in to change notification settings - Fork 52
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
Context preservation fails for zlib.unzip
#22
Comments
cc @creationix |
@rf which version of node ? Looking at the source code I dont see anything different between gzip & unzip in node. |
I was running the test with v0.10.26. I just tried with node v0.10.34 and I'm still seeing my test fail. I looked at the source as well and figured the same thing, so I'm not sure what's going on here. |
@rf try running the tests in different orders, it might not be gzip vs unzip, it might be the first one wins & second one fails. |
Tried that too. The And the |
I'll take a look. It's possible there's something wacky with native bindings going on under the hood and the default wrapping method won't work for zlib. Thanks for the report! |
Here's a failing test on my fork. It seems to work in the case of
zlib.gzip
but when I try to useunzip
my global variable doesn't get preserved. If you replace the call tozlib.unzip
with aprocess.nextTick
, it'll work.Am I misunderstanding the use of this, or is this a bug in the way
zlib
is wrapped?@sh1mmer @Raynos @othiym23
The text was updated successfully, but these errors were encountered: