Skip to content

net.autoSelectFamilyAttemptTimeoutDefault should not be constant #52082

Closed as not planned
Closed as not planned
net.autoSelectFamilyAttemptTimeoutDefault should not be constant#52082
Labels
feature requestIssues requesting new Node.js features.netIssues and PRs related to the net subsystem.staleIssues and PRs marked stale due to inactivity and scheduled for automatic closure.

Description

@callmebar
callmebar
opened on Mar 14, 2024

What is the problem this feature will solve?

I have slow Internet connection and when a domain with multiple ip appears, I always get ETIMEDOUT because the connection can not be established in default autoSelectFamilyAttemptTimeoutDefault=250ms. There are a lot of npm packages that use node:net, and it'not possible to wait until all of them implement a mechanism to deal with autoSelectFamilyAttemptTimeout.

What is the feature you are proposing to solve the problem?

I believe it should be fixed by setting autoSelectFamilyAttemptTimeoutDefault in NODE_OPTIONS

What alternatives have you considered?

Now, it's possible to change this parameter by calling net.setDefaultAutoSelectFamilyAttemptTimeout, but I can call it only in my own code, but not from other applications (e.g. yarn), so it won't help in most cases.
Alternatively, you can just increase the default parameter, but it is not flexible solution.

Activity

  1. callmebar
    added
    feature requestIssues requesting new Node.js features.
    on Mar 14, 2024
  2. github-project-automation
    added this to Node.js feature requestson Mar 14, 2024
  3. github-project-automation
    moved this to Pending Triage in Node.js feature requestson Mar 14, 2024
  4. marco-ippolito
    added
    netIssues and PRs related to the net subsystem.
    on Mar 15, 2024

  5. marco-ippolito commented on Mar 15, 2024

    @marco-ippolito
    marco-ippolito
    on Mar 15, 2024
    Member

    cc @ShogunPanda

  6. ShogunPanda commented on Mar 15, 2024

    @ShogunPanda
    ShogunPanda
    on Mar 15, 2024
    Contributor

    I'm totally in for this. Would you like to send a PR? Otherwise I'll try to implement shortly.

  7. jazelly commented on Aug 25, 2024

    @jazelly
    jazelly
    on Aug 25, 2024
    Member

    This has probably been fixed by #52474

  8. github-actions commented on Feb 22, 2025

    @github-actions
    github-actionsbot
    on Feb 22, 2025 – with GitHub Actions
    Contributor

    There has been no activity on this feature request for 5 months. To help maintain relevant open issues, please add the never-stale Issues and PRs exempt from automated stale handling. label or close this issue if it should be closed. If not, the issue will be automatically closed 6 months after the last non-automated comment.
    For more information on how the project manages feature requests, please consult the feature request management document.

  9. github-actions
    added
    staleIssues and PRs marked stale due to inactivity and scheduled for automatic closure.
    on Feb 22, 2025

  10. github-actions commented on Mar 24, 2025

    @github-actions
    github-actionsbot
    on Mar 24, 2025 – with GitHub Actions
    Contributor

    There has been no activity on this feature request and it is being closed. If you feel closing this issue is not the right thing to do, please leave a comment.

    For more information on how the project manages feature requests, please consult the feature request management document.

  11. github-actions
    closed this as not plannedon Mar 24, 2025
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

    feature requestIssues requesting new Node.js features.netIssues and PRs related to the net subsystem.staleIssues and PRs marked stale due to inactivity and scheduled for automatic closure.

    Type

    No type

    Projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions