This repository has been archived by the owner on Aug 7, 2019. It is now read-only.
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.
Issue
Since
transferIn
is asynchronous, it's possible to have multiple async loops (seewebUsbDevice.read()
) to calltransferIn
, causing some packets to end up in the wrong read loop.This manifests by a look expecting the first packet to have a header with a
messageLength
, but since the packet it receives is not really a first packet, but the middle of some other read, the read length is incorrect and causes an error when attempting to create a massively large array.Resolution
Use
p-queue
to add an async queue with a concurrency of 1 to only allow one message and response to the device at a time.Extra
This PR also simplifies some code around reading message length and concatenating packets.