Repository navigation
net.autoSelectFamilyAttemptTimeoutDefault should not be constant #52082
Description
Activity
cc @ShogunPanda
I'm totally in for this. Would you like to send a PR? Otherwise I'll try to implement shortly.
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.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.
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 withautoSelectFamilyAttemptTimeout.What is the feature you are proposing to solve the problem?
I believe it should be fixed by setting
autoSelectFamilyAttemptTimeoutDefaultinNODE_OPTIONSWhat 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.