chore(net): use native happy eyeballs instead of the manual implementation - #42240
Pavel Feldman (pavelfeldman) merged 1 commit into
Conversation
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
9c7a55b to
ba36e11
Compare
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
|
Hi, I'm the Playwright bot and I took a look at the CI failures here. 🔴 One failure is caused by this PR
DetailsOverall: the latest Caused by this PR
Pre-existing flake / infra
Uncertain
Triaged by the Playwright bot. Triaged by the Playwright bot - agent run |
ba36e11 to
f7d9f91
Compare
Test results for "MCP"8101 passed, 1311 skipped Merge workflow run. |
Test results for "tests 1"20 flaky51105 passed, 1208 skipped Merge workflow run. |
dffe620
into
microsoft:main
Summary
utils/happyEyeballs.ts); Node.js 20+ races connection attempts natively viaautoSelectFamily, which is enabled by default.lookupoption (dualStackLookupinutils/network.ts): a family-agnostic getaddrinfo can miss::1forlocalhost(AI_ADDRCONFIG filtering,/etc/hostsmapping::1toip6-localhostonly), breaking localhost servers bound to a single family.lookup/connect/secureConnectevents;__testHookLookupis adapted into the standardlookupoption.Fixes: #42193