Skip to content
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

doc: dns.lookup() documentation error code #27625

Closed
wants to merge 1 commit into from
Closed

doc: dns.lookup() documentation error code #27625

wants to merge 1 commit into from

Conversation

jvelezpo
Copy link
Contributor

@jvelezpo jvelezpo commented May 9, 2019

dns.lookup() will always return ENOTFOUND on a empty lookup
or when the host not found.
https://github.com/nodejs/node/blob/master/lib/internal/errors.js#L503

Fixes: #27604

  • make -j4 test (UNIX), or vcbuild test (Windows) passes
  • documentation is changed or added
  • commit message follows commit guidelines

dns.lookup() will always return ENOTFOUND on a empty lookup
or when the host not found.
https://github.com/nodejs/node/blob/master/lib/internal/errors.js#L503

Fixes: #27604
@nodejs-github-bot nodejs-github-bot added dns Issues and PRs related to the dns subsystem. doc Issues and PRs related to the documentations. labels May 9, 2019
@richardlau
Copy link
Member

dns.lookup() will always return ENOTFOUND on a empty lookup
or when the host not found.
https://github.com/nodejs/node/blob/master/lib/internal/errors.js#L503

What about (from the docs) when the lookup fails in other ways such as no available file descriptors?

@Trott Trott added the author ready PRs that have at least one approval, no pending requests for changes, and a CI started. label May 10, 2019
@Trott
Copy link
Member

Trott commented May 10, 2019

@Trott
Copy link
Member

Trott commented May 13, 2019

dns.lookup() will always return ENOTFOUND on a empty lookup
or when the host not found.
https://github.com/nodejs/node/blob/master/lib/internal/errors.js#L503

What about (from the docs) when the lookup fails in other ways such as no available file descriptors?

I experimented and seemed to get ENOTFOUND in that situation too. #27604 (comment)

@Trott
Copy link
Member

Trott commented May 13, 2019

Landed in fd8d5e7

@Trott Trott closed this May 13, 2019
Trott pushed a commit to Trott/io.js that referenced this pull request May 13, 2019
dns.lookup() will always return ENOTFOUND on a empty lookup
or when the host not found.
https://github.com/nodejs/node/blob/master/lib/internal/errors.js#L503

Fixes: nodejs#27604

PR-URL: nodejs#27625
Reviewed-By: Rich Trott <rtrott@gmail.com>
Reviewed-By: James M Snell <jasnell@gmail.com>
@jvelezpo jvelezpo deleted the docs-dns branch May 14, 2019 12:34
targos pushed a commit that referenced this pull request May 14, 2019
dns.lookup() will always return ENOTFOUND on a empty lookup
or when the host not found.
https://github.com/nodejs/node/blob/master/lib/internal/errors.js#L503

Fixes: #27604

PR-URL: #27625
Reviewed-By: Rich Trott <rtrott@gmail.com>
Reviewed-By: James M Snell <jasnell@gmail.com>
@BridgeAR BridgeAR mentioned this pull request May 21, 2019
4 tasks
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
author ready PRs that have at least one approval, no pending requests for changes, and a CI started. dns Issues and PRs related to the dns subsystem. doc Issues and PRs related to the documentations.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

dns.lookup() documentation error code
6 participants