-
Notifications
You must be signed in to change notification settings - Fork 393
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
Module doesn't self-register from a worker thread #831
Comments
nodejs/node#21783 (comment) , the solution seems quite simple. |
I'm experiencing the same problem. I'm not directly using the lib in the worker thread, but it is imported with other modules and crashes. |
This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. |
This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. |
any update on this? Still cannot open up workers utilizing node-rdkafka |
A workaround for Blizzard#831
A workaround for Blizzard#831 upped the version
Environment Information
Steps to Reproduce
Additional context
Even though this issue relates to nodejs internal implementation of workers, nodejs developers wont fix it. However it can be fixed by making native module context-aware. Here is an example for node-lzo: schroffl/node-lzo#11
The text was updated successfully, but these errors were encountered: