Repository navigation
Queue Bluetooth writes so fast typing no longer drops characters - #25
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
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.
Fixes #24.
Web Bluetooth allows one GATT operation at a time. The REPL sent every keystroke as its own
writeValue, so typing fast started a write while the last was still in flight; the browser refused it with "GATT operation already in progress" and the character was lost.Writes in the Bluetooth transport now go through a queue. Each
writeValuewaits for the one before it, and keystrokes that pile up while a write is on the air are sent together in one write, never larger than the characteristic's size.A new test uses a mocked characteristic that throws that error whenever two writes overlap. It fails on the old code (every keystroke after the first is refused) and passes now.