-
Notifications
You must be signed in to change notification settings - Fork 10.3k
Fix SignalR typescript tests with Chrome SameSite reaction #25283
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
Conversation
Thanks @BrennanConroy - FYI test-only fixes can be proactively merged unless you have concern about the risk to the build. |
Mac passed on this PR which was the remaining failures on #25090 which had half of this change. I've verified before and after on my Windows machine as well, so confident this wont break. If someone wants they can merge then 👍 |
@ajaybhargavb the validation build for this PR failed due to build ordering issues. Something has destabilized the release/5.0 branch significantly because I've seen this a few times in the last week. Please use some of your ops-on-call time to figure out what's busted. |
@ajaybhargavb yes please. And, please also mention that issue as important when handing off your ops rotation. |
Filed #25293 |
* Fix Typescript tests * fixup
@BrennanConroy thanks for opening #25473 too❕ You'll probably need to |
* Set SameSiteMode for cookies in authentication tests (#25281) * Fix SignalR typescript tests with Chrome SameSite reaction (#25283) * Disable template tests that use Selenium Co-authored-by: Brennan <[email protected]> Co-authored-by: Doug Bunting <[email protected]>
Chrome released its SameSite cookie support on 8/25 which broke some tests that used cookies cross-domain. This fixes the tests.