fix(desktop): bound control replies and observe paste latency - #98
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 stalled clipboard-ready write could hold the desktop control loop indefinitely; input ACK and heartbeat replies also inherited the 30-second media budget. All control replies now use a two-second deadline and reset the owning stream on failure without replaying input.
Keyboard/button ACK histories are separate from pointer traffic. Explicit paste timing binds the exact transfer ID and size on the viewer clock, counts cancellation/eviction/unmatched replies, and records pending or completed delays in bounded incident windows. Metadata excludes content, keys and coordinates.
Validation: 100 desktop viewer library tests and strict native workspace clippy passed. New regressions cover a blocked partial reply, ordered successful replies, motion masking, clipboard correlation/bounds and delayed incident capture. Full native workspace tests and cross-platform CI are in progress; native sustained application response remains unqualified.