| FazBrowse GitHub Viewer | Trending | | Home |
| Tools: [Download Repo ZIP] [Original HTTPS Page] |
Sorry, something went wrong.
|
CI: https://ci.nodejs.org/job/node-test-pull-request/6839/ |
Sorry, something went wrong.
|
Error messages vary on different machines..loosen up the message validation and try again. CI: https://ci.nodejs.org/job/node-test-pull-request/6850/ |
Sorry, something went wrong.
|
Something is wrong with net.connect({fd: TCPfd})(keep getting ENOTCONN or flaky libuv assertion failures)..probably has something to do with the state management. I'll remove it from this PR for now and investigate later. Pipe fd works fine though. @jasnell PTAL, thanks. CI is green now: https://ci.nodejs.org/job/node-test-pull-request/6867/ |
Sorry, something went wrong.
|
Still LGTM! |
Sorry, something went wrong.
PR-URL: #11847 Reviewed-By: James M Snell <jasnell@gmail.com>
PR-URL: nodejs#11847 Reviewed-By: James M Snell <jasnell@gmail.com>
|
This PR need backport to v7 |
Sorry, something went wrong.
|
@joyeecheung Should this be backported to v6.x-staging? If yes please follow the guide and raise a backport PR, if no let me know or add the dont-land-on label. If it is backported, the PR should include #12601. |
Sorry, something went wrong.
| Back | FazBrowse Home | New Git URL |
Related: #11761
This PR adds coverage to more calling patterns of net.connect:
Checklist
Affected core subsystem(s)
test, net