-
Notifications
You must be signed in to change notification settings - Fork 15k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
feat: support dns-result-order Node.js cli flag #39376
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
API LGTM
926ee4c
to
7e0ffa6
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
API LGTM
The patch fails to apply. |
Co-authored-by: Erick Zhao <erick@hotmail.ca>
7e0ffa6
to
4d0608f
Compare
|
Release Notes Persisted
|
I have automatically backported this PR to "25-x-y", please check out #39500 |
I have automatically backported this PR to "26-x-y", please check out #39501 |
* feat: support dns-result-order Node.js cli flag * chore: update docs Co-authored-by: Erick Zhao <erick@hotmail.ca> * chore: remove patch --------- Co-authored-by: Erick Zhao <erick@hotmail.ca>
* feat: support dns-result-order Node.js cli flag * chore: update docs Co-authored-by: Erick Zhao <erick@hotmail.ca> * chore: remove patch --------- Co-authored-by: Erick Zhao <erick@hotmail.ca>
Description of Change
This allows applications that load 3-party plugins to provide the legacy behavior with a process wide flag. There is also dns.setDefaultResultOder but it is per thread API so cannot be used effectively in a plugin process.
Checklist
npm test
passesRelease Notes
Notes: Add support for --dns-result-order Node.js cli flag