Revert the change of network interfaces family from String to Integer #43014
Labels
dns
Issues and PRs related to the dns subsystem.
tsc-agenda
Issues and PRs to discuss during the meetings of the TSC.
Comments
Apollon77
changed the title
|
Seeing a lot a pain coming out of this breaking change. |
|
cc @nodejs/tsc I think I'd lean towards reverting #41431, even though reverting the change would itself be breaking. Or at least restoring the family attribute on network interface objects to a string. |
Trott
added
the
tsc-agenda
|
Agree, this change has been more disruptive than I think we'd have liked. I'd be +1 on a revert. I have seen that some of the ecosystem has already spent time investigating and adjusting to this change. Would a full revert cause additional disruption at this point? I'm curious if there's a way to adequately mitigate the impact of the change without causing further disruption. Would the suggestions in #41431 (comment) be sufficient? |
|
I assume (at least from the changes I have "seen" and because of needed nodejs backward compatibility) most simply added it as alternative to support both variants ... So a revert should (!) for most just lead to a "dead code OR clause" |
Merged
aduh95
added a commit
to aduh95/node
that referenced
this issue
May 11, 2022
aduh95
added a commit
to aduh95/node
that referenced
this issue
May 11, 2022
This reverts commits 68fb0bf, 4ad342a, and 3a26db9. Fixes: nodejs#43014
aduh95
added a commit
to aduh95/node
that referenced
this issue
May 11, 2022
aduh95
added a commit
to aduh95/node
that referenced
this issue
May 11, 2022
This reverts commits 68fb0bf, 4ad342a, and 3a26db9. Fixes: nodejs#43014
aduh95
added a commit
to aduh95/node
that referenced
this issue
May 21, 2022
aduh95
added a commit
to aduh95/node
that referenced
this issue
May 21, 2022
This reverts commits 68fb0bf, 4ad342a, and 3a26db9. Fixes: nodejs#43014
|
Inthe TSC meeting (at least as I understand the minutes) it was decided to revert the "integrater family back to Strings" ... should be in Node.js 18.2. Thank you very much for this! |
8 tasks
aduh95
added a commit
to aduh95/node
that referenced
this issue
Jun 5, 2022
aduh95
added a commit
to aduh95/node
that referenced
this issue
Jun 5, 2022
This reverts commits 68fb0bf, 4ad342a, and 3a26db9. Fixes: nodejs#43014
danielleadams
pushed a commit
that referenced
this issue
Jun 16, 2022
Refs: #43014 PR-URL: #43054 Fixes: #43014 Reviewed-By: Matteo Collina <[email protected]> Reviewed-By: Darshan Sen <[email protected]> Reviewed-By: Beth Griggs <[email protected]> Reviewed-By: Rich Trott <[email protected]> Reviewed-By: Michaël Zasso <[email protected]> Reviewed-By: Michael Dawson <[email protected]> Reviewed-By: Ruben Bridgewater <[email protected]>
xnuk
added a commit
to xnuk/souffle
that referenced
this issue
Jul 5, 2022
Note: nodejs/node#43014 This reverts commit 0cd9dc6.
AdamMajer
added a commit
to AdamMajer/node
that referenced
this issue
Aug 1, 2022
As a consequence of nodejs#43014 , server sockets and others, once connected, report string family names. But when feeding these to Socket.connect(), it passes these to host resolution with a string for family while a numeric family is expected internally. This results wrong hints flags to be set and resolution to fail. As solution, is to add ability to handle both numeric and string family names when doing lookup and connect. Fixes: nodejs#44003
AdamMajer
added a commit
to AdamMajer/node
that referenced
this issue
Aug 1, 2022
As a consequence of nodejs#43014 , server sockets and others, once connected, report string family names. But when feeding these to Socket.connect(), it passes these to host resolution with a string for family while a numeric family is expected internally. This results in wrong hints flags to be set and resolution to fail. As solution, is to add ability to handle both numeric and string family names when doing lookup and connect. Fixes: nodejs#44003
nodejs-github-bot
pushed a commit
that referenced
this issue
Aug 3, 2022
As a consequence of #43014 , server sockets and others, once connected, report string family names. But when feeding these to Socket.connect(), it passes these to host resolution with a string for family while a numeric family is expected internally. This results in wrong hints flags to be set and resolution to fail. As solution, is to add ability to handle both numeric and string family names when doing lookup and connect. Fixes: #44003 PR-URL: #44083 Reviewed-By: Paolo Insogna <[email protected]> Reviewed-By: Luigi Pinca <[email protected]>
danielleadams
pushed a commit
that referenced
this issue
Aug 16, 2022
As a consequence of #43014 , server sockets and others, once connected, report string family names. But when feeding these to Socket.connect(), it passes these to host resolution with a string for family while a numeric family is expected internally. This results in wrong hints flags to be set and resolution to fail. As solution, is to add ability to handle both numeric and string family names when doing lookup and connect. Fixes: #44003 PR-URL: #44083 Reviewed-By: Paolo Insogna <[email protected]> Reviewed-By: Luigi Pinca <[email protected]>
ruyadorno
pushed a commit
that referenced
this issue
Aug 23, 2022
As a consequence of #43014 , server sockets and others, once connected, report string family names. But when feeding these to Socket.connect(), it passes these to host resolution with a string for family while a numeric family is expected internally. This results in wrong hints flags to be set and resolution to fail. As solution, is to add ability to handle both numeric and string family names when doing lookup and connect. Fixes: #44003 PR-URL: #44083 Reviewed-By: Paolo Insogna <[email protected]> Reviewed-By: Luigi Pinca <[email protected]>
Fyko
pushed a commit
to Fyko/node
that referenced
this issue
Sep 15, 2022
As a consequence of nodejs#43014 , server sockets and others, once connected, report string family names. But when feeding these to Socket.connect(), it passes these to host resolution with a string for family while a numeric family is expected internally. This results in wrong hints flags to be set and resolution to fail. As solution, is to add ability to handle both numeric and string family names when doing lookup and connect. Fixes: nodejs#44003 PR-URL: nodejs#44083 Reviewed-By: Paolo Insogna <[email protected]> Reviewed-By: Luigi Pinca <[email protected]>
juanarbol
pushed a commit
that referenced
this issue
Oct 3, 2022
As a consequence of #43014 , server sockets and others, once connected, report string family names. But when feeding these to Socket.connect(), it passes these to host resolution with a string for family while a numeric family is expected internally. This results in wrong hints flags to be set and resolution to fail. As solution, is to add ability to handle both numeric and string family names when doing lookup and connect. Fixes: #44003 PR-URL: #44083 Reviewed-By: Paolo Insogna <[email protected]> Reviewed-By: Luigi Pinca <[email protected]>
juanarbol
pushed a commit
that referenced
this issue
Oct 4, 2022
As a consequence of #43014 , server sockets and others, once connected, report string family names. But when feeding these to Socket.connect(), it passes these to host resolution with a string for family while a numeric family is expected internally. This results in wrong hints flags to be set and resolution to fail. As solution, is to add ability to handle both numeric and string family names when doing lookup and connect. Fixes: #44003 PR-URL: #44083 Reviewed-By: Paolo Insogna <[email protected]> Reviewed-By: Luigi Pinca <[email protected]>
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Version
18.x
Platform
any
Subsystem
dns?
What steps will reproduce the bug?
see #41431 (review)
How often does it reproduce? Is there a required condition?
always
What is the expected behavior?
The family is backward compatible a string and not an integer thatbreaks many modules
What do you see instead?
family is an integer breaking many libraries
Additional information
Please see the comments in the linked PR and consider a "fix" fo this breaking change
The text was updated successfully, but these errors were encountered: