Skip to content
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

net.connect issue with Node.js 7.10.0 #109

Open
watson opened this issue May 5, 2017 · 1 comment
Open

net.connect issue with Node.js 7.10.0 #109

watson opened this issue May 5, 2017 · 1 comment

Comments

@watson
Copy link
Collaborator

watson commented May 5, 2017

A commit recently landed in Node core that was released as v7.10.0 two days ago.

It breaks async-listener because net.connect no longer calls Socket.prototype.connect. Furthermore, it's not possible to simply monkey-patch net.connect because it's being called internally in node by simply referencing the connect function and not the exports.connect function.

I'm working on fixing this together with @cjihrig and @jasnell. See nodejs/node#12852 for details.

It will most likely be released as v7.10.1.

@watson watson changed the title Issue with Node.js 7.10.0 net.connect issue with Node.js 7.10.0 May 5, 2017
@watson
Copy link
Collaborator Author

watson commented May 8, 2017

The work to fix this have now been moved to nodejs/node#12861

watson added a commit to watson/async-listener that referenced this issue Jun 15, 2017
Because issue othiym23#109 have
not yet been solved for Node.js 7, the test suite currently fails when
running on the latest version of Node.js 7 (v7.10.0 as of this commit).

This commit allows 7.x to fail, but adds an extra build for 7.9.0 which
is know to be good.

This should be reverted when/if Node.js 7 is patched accordingly.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant