fix(speedtest): fail-open prefill check - #2255
Merged
Merged
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
A user session where ALL endpoints failed the reachability precheck (VPN/extension/network-level blocking) got its input list wiped to zero, bricking the tool. Verified server-side that the cohort endpoints are healthy (POST with Origin returns 200 + allow-origin:*) and the staging CSP is correct, so an all-fail signal is environmental, not per-endpoint CORS. The precheck now only drops endpoints on a DIFFERENTIAL signal (some pass, some fail); an all-fail keeps the full list and lets the real test classify, with a console warning.