Sitelet https://github.com/nodejs/node/issues/43014
Skip to content

Revert the change of network interfaces family from String to Integer #43014

Description

@Apollon77

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

Activity

  1. changed the title [-]Revert the change of network interfaces family from Striung to Integer[/-] [+]Revert the change of network interfaces family from String to Integer[/+] on May 9, 2022
  2. joe-hilling commented on May 9, 2022

    @joe-hilling

    Seeing a lot a pain coming out of this breaking change.

  3. richardlau commented on May 9, 2022

    @richardlau
    Member

    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.

  4. added
    tsc-agendaIssues and PRs to discuss during Technical Steering Committee meetings.
    on May 9, 2022
  5. Trott commented on May 9, 2022

    @Trott
    Member

    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.

    I tentatively agree.

    @aduh95 @mcollina

  6. BethGriggs commented on May 9, 2022

    @BethGriggs
    Member

    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?

  7. Apollon77 commented on May 9, 2022

    @Apollon77
    Author

    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"

  8. added
    dnsIssues and PRs related to the dns subsystem.
    on May 9, 2022
  9. Apollon77 commented on May 22, 2022

    @Apollon77
    Author

    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!

  10. 7 remaining items

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    dnsIssues and PRs related to the dns subsystem.tsc-agendaIssues and PRs to discuss during Technical Steering Committee meetings.

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions