-
Notifications
You must be signed in to change notification settings - Fork 3.9k
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
Reapply "fix(har timing): record connect timing for proxied connections" (#32855) #33003
Conversation
…ions" (microsoft#32989) This reverts commit 1b589c4.
Test results for "tests others"20556 passed, 491 skipped Merge workflow run. |
Test results for "tests 1"1 flaky35860 passed, 619 skipped Merge workflow run. |
@@ -515,11 +514,21 @@ export abstract class APIRequestContext extends SdkObject { | |||
}), | |||
); | |||
|
|||
// when using socks proxy, having the socket means the connection got established | |||
if (agent instanceof SocksProxyAgent) |
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.
this should be also the case for HttpsProxyAgent? So maybe we should check for just agent thruthyness there?
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.
HTTPSProxyAgent emits its own separate event that's more precise, so we use that: https://github.com/microsoft/playwright/pull/33003/files#diff-dc06386362e7da98cd82627a6b4f337ae01799a53cac4f208089b2b89c4dc832R527-R529
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.
LGTM % comment.
Test results for "tests 2"2 fatal errors, not part of any test 56 flaky238809 passed, 9422 skipped, 13 did not run Merge workflow run. |
…onnections" (microsoft#32855) (microsoft#33003)" This reverts commit 042161e.
…d connect timing for proxied connections" (microsoft#32855) (microsoft#33003)"
This reapplies what we reverted in #32989.
Max and me debugged this, and found that the test failures come from SOCKS proxy now preferring IPv6 over IPv4. We've updated the tests and made sure that this doesn't mask any breaking change.
I'm enabling CQ1 to make sure we don't oversee any other CI failures.