Skip to content

Conversation

@jasnell
Copy link
Member

@jasnell jasnell commented Aug 27, 2016

Checklist
  • make -j4 test (UNIX), or vcbuild test nosign (Windows) passes
  • documentation is changed or added
  • commit message follows commit guidelines
Affected core subsystem(s)

doc

Description of change

Document that listen can be called multiple times.

Fixes: #4646

@jasnell jasnell added http Issues or PRs related to the http subsystem. doc Issues and PRs related to the documentations. net Issues and PRs related to the net subsystem. labels Aug 27, 2016
@cjihrig
Copy link
Contributor

cjihrig commented Aug 27, 2016

LGTM

@mscdex
Copy link
Contributor

mscdex commented Aug 27, 2016

Commit message is too long

@addaleax
Copy link
Member

Going maybe too off-topic here… is there any chance the length of the title could be renegotiated to something longer or to at least not including the subsystem prefix? 50 characters is a pretty hard limit when you need to include something like child_process: and/or are a non-native speaker with reduced vocabulary…

jasnell added a commit that referenced this pull request Aug 29, 2016
Fixes: #4646 PR-URL: #8294 Reviewed-By: Colin Ihrig <cjihrig@gmail.com>
@jasnell
Copy link
Member Author

jasnell commented Aug 29, 2016

Landed in 488d37b

@jasnell jasnell closed this Aug 29, 2016
@Fishrock123 Fishrock123 mentioned this pull request Sep 6, 2016
Fishrock123 pushed a commit to Fishrock123/node that referenced this pull request Sep 8, 2016
Fixes: nodejs#4646 PR-URL: nodejs#8294 Reviewed-By: Colin Ihrig <cjihrig@gmail.com>
Fishrock123 pushed a commit that referenced this pull request Sep 9, 2016
Fixes: #4646 PR-URL: #8294 Reviewed-By: Colin Ihrig <cjihrig@gmail.com>
@MylesBorins
Copy link
Contributor

This does not land cleanly in LTS. Added dont-land label. Please feel free to manually backport

eduardbme added a commit to eduardbme/node that referenced this pull request Sep 2, 2017
Problem: It's possible to run listen() on a net.Server that's already listening to a port. The result is silent failure, with the side effect of changing the connectionKey and or pipeName. Solution: throw an error if listen method called more than once. close() method should be called between listen() method calls. Refs: nodejs#8294 Fixes: nodejs#6190 Fixes: nodejs#11685
mcollina pushed a commit that referenced this pull request Sep 4, 2017
Problem: It's possible to run listen() on a net.Server that's already listening to a port. The result is silent failure, with the side effect of changing the connectionKey and or pipeName. Solution: throw an error if listen method called more than once. close() method should be called between listen() method calls. Refs: #8294 Fixes: #6190 Fixes: #11685 PR-URL: #13149 Reviewed-By: Matteo Collina <matteo.collina@gmail.com> Reviewed-By: Colin Ihrig <cjihrig@gmail.com> Reviewed-By: Ruben Bridgewater <ruben@bridgewater.de> Reviewed-By: James M Snell <jasnell@gmail.com> Reviewed-By: Joyee Cheung <joyeec9h3@gmail.com>
addaleax pushed a commit to addaleax/ayo that referenced this pull request Sep 5, 2017
Problem: It's possible to run listen() on a net.Server that's already listening to a port. The result is silent failure, with the side effect of changing the connectionKey and or pipeName. Solution: throw an error if listen method called more than once. close() method should be called between listen() method calls. Refs: nodejs/node#8294 Fixes: nodejs/node#6190 Fixes: nodejs/node#11685 PR-URL: nodejs/node#13149 Reviewed-By: Matteo Collina <matteo.collina@gmail.com> Reviewed-By: Colin Ihrig <cjihrig@gmail.com> Reviewed-By: Ruben Bridgewater <ruben@bridgewater.de> Reviewed-By: James M Snell <jasnell@gmail.com> Reviewed-By: Joyee Cheung <joyeec9h3@gmail.com>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

doc Issues and PRs related to the documentations. http Issues or PRs related to the http subsystem. net Issues and PRs related to the net subsystem.

5 participants