Repository navigation
Fix stale blocking warnings and QUIC failure fan-out - #80
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 working HTTP/3 VPN could keep a suspected-blocking warning indefinitely: successful proxy tunnels did not reset failure evidence or clear warnings, and several streams closing with one QUIC session counted as independent failures. The failure window also advanced after every failure rather than bounding the whole sequence.
Count failures in a fixed 60-second window, deduplicate QUIC-session failures, and reset evidence on a successful end-to-end proxy tunnel. Forward successful tunnel diagnostics to the service without a notification update for every stream. Clear only the blocking warning and any exhausted-failover notice; preserve actual profile-switch notices and unrelated warnings. Local bypass, a successful first Jump hop, stale profiles and a stopped VPN cannot clear the warning. Restore ownership of persisted exhausted-failover warnings after service recreation.
TCP-over-MASQUE I/O failures now carry the same local QUIC session number as UDP/open-stream failures, allowing shared-session deduplication without endpoint data. EN/RU metrics documentation describes the behavior.
Validation: Bundler/Fastlane native tests (201, race enabled) and Android checks (268 JVM/Compose tests, lint, debug and unsigned release APKs) pass. Regression tests cover shared-session fan-out, bounded failure windows, success resetting evidence, warning removal, preservation of other warnings, and stale/stopped-session guards. Independent API 26/API 35 integration checks run in PR CI.