[v8.x backport] net: remove Socket.prototype.listen#21176
[v8.x backport] net: remove Socket.prototype.listen#21176codebytere wants to merge 1 commit intonodejs:v8.x-stagingfrom codebytere:backport-13735-to-v8.x
Conversation
The function was never documented and now throws a TypeError if used. PR-URL: #13735 Reviewed-By: Colin Ihrig <cjihrig@gmail.com> Reviewed-By: Ben Noordhuis <info@bnoordhuis.nl> Reviewed-By: Anatoli Papirovski <apapirovski@mac.com>
|
Okay, tests finally passed. @MylesBorins shall we land this? |
|
My only concern with landing this is that it has the risk of breaking something on 8.x that we don't know about. I'm not sure this actually makes sense for LTS at the moment without someone else chiming in... specifically because we don't really have anything huge to gain by landing it, but if we have even a 1% risk of breaking things we likely shouldn't. Perhaps we should run citgm? |
|
@MylesBorins it's an undocumented and defunct method, and I hope nobody from the ecosystem is using it, but yeah, why not run CITGM and know for sure? |
|
Landing on v8.x this seems to break our LTS policy..this has been released in v9.x but has never been tested in older release lines. |
|
@joyeecheung is there a way i can tell if that's the case from looking at PRs which have the |
|
@codebytere Unfortunately, we are behind on triaging pull requests for backportingβ¦ Iβve manually unmarked the original PR for backporting, but I donβt really have a good way for you tell which ones should be backported, other than comparing a change to our LTS policies (no potential breaking changes of any kind, unless the API is experimental). Sorry about that. |
|
@TimothyGu no worries, thanks! Should this backport be closed? |
|
@codebytere yes, please close this if it's okay. |
|
@codebytere What @TimothyGu said, sorry about the confusion. We probably should've marked that PR |
|
thanks @joyeecheung, appreciate the context! |
Original PR: #13735
Checklist
make -j4 testpasses