Require two consecutive readings before rebuilding a starved tap - #40
Merged
Conversation
…tarved tap A single latency sample can be stale after a long quiet stretch (observed on macOS 26), so the watchdog now treats the first bad reading as suspect and only convicts on a second consecutive one. Reading the tap list resets the window server's accumulator, which is what makes the confirmation reliable: a stale sample cannot survive its own read.
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.
Summary
Test plan
swift test --filter TapStarvationPolicyTests— 8 tests)just dev— confirm app launches and shortcuts work🤖 Generated with Claude Code