Conversation
Fake peer that acts as a client or a server at each protocol version and checks every message against the formats Synergy 1.x, Barrier and Input Leap use, so a mismatch both halves of Deskflow agree on still fails.
nbolton
marked this pull request as ready for review
September 18, 2026 17:48
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.
Generated by Claude
Companion to deskflow/deskflow#10069, the key repeat protocol fix. No Jira issue.
Test steps
With a Deskflow server running from the GUI and a screen named
harnessin its layout, runpython3 protocol_harness.py client --name harness --versions 1.8,1.6 --wait 20. When it prompts, push the pointer onto the harness screen, hold a key for two seconds, then move back.Expect:
ok DKRPlines andPASSfor both versions on the fix branch; on master the 1.6 run reports six leftover bytes and fails.Run
python3 protocol_harness.py server, then start a Deskflow client from the GUI pointed at this machine.Expect: 1.8, 1.7 and 1.6 each fully "parsed and answered", 1.5 refused,
PASSon all four.