-
Notifications
You must be signed in to change notification settings - Fork 1.9k
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
Can't create a redis Client under Node v7.7+ #1210
Comments
Running without PM2 I get a error elsewhere:
So I'm still digging |
Looks like something has changed in node 7.7, tested in 7.7.0 and 7.7.2 same issue. Running via node instead of a pm2 start call just means that another module trips before redis does I think? I wonder if related to https://github.com/nodejs/node/blob/master/doc/changelogs/CHANGELOG_V7.md#7.7.1 "Node.js 7.7.0 contains a bug that will prevent all native modules from building, this patch should fix the issue. Apologies to everyone who was affected by 7.7.0." |
Cross linking - tediousjs/tedious#532 |
That is a Node.js bug. Please always check the stack traces to determine the original of the error. |
No argument there, I just opened the issue, whilst I was working through the problem and didn't self close to leave a trace issue for others until Node 7.7.3 drops (As of course, the issue occurred on production and YAY live debugging) |
Tediuous made this change: tediousjs/tedious@ba01a85 to combat the node bug. Is it worth making the same/similar socket fix in case this a is node deprecation possibility in the future @BridgeAR |
@BarryCarlyon thanks for the hint. I do not have any time to look into this right now. If you find a way to have a work around for the bug, please feel free to open a pull request for it :-) |
[gitter]: https://gitter.im/NodeRedis/node_redis?utm_source=badge&utm_medium=badge&utm_campaign=pr-badge
Repro:
Output:
The text was updated successfully, but these errors were encountered: