-
Notifications
You must be signed in to change notification settings - Fork 29.6k
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
http: use localAddress
instead of path
#5190
Conversation
/cc @nodejs/http |
LGTM |
LGTM. Maybe this is something that we should run citgm on first? /cc @thealphanerd |
@nodejs/ctc ... anyone have any concerns with this one? |
7da4fd4
to
c7066fb
Compare
Running test suites one more time. Is anyone opposed to this landing if everything is green? ci: https://ci.nodejs.org/job/node-test-pull-request/2551/ edit: we are having issues with citgm in CI right now... figuring out what is going on, ignore results in the mean time |
LGTM but there are a few style violations in the test that need to be fixed. |
Fix `options` usage on `lib/_http_agent.js` for the Legacy API. Fixes: nodejs#5051
@bnoordhuis thanks! I've updated the test file, and there are no more jslint errors. |
citgm: https://ci.nodejs.org/view/Node.js-citgm/job/thealphanerd-smoker/261/ Hopefully the CI problems we were seeing yesterday should be resolved |
CI is green, citgm is taking too long to load here. |
LGTM |
citgm: https://ci.nodejs.org/job/thealphanerd-smoker/270/ if it is green I will land this |
CITGM is green. Landed in fe77de1, thanks Dirceu. |
how long should this stay on v6 before a backport? |
ping @nodejs/http re: backport |
@nodejs/lts is this something we want to see land on v4.x? |
Fix
options
usage onlib/_http_agent.js
for the Legacy API.Fixes: #5051