Handle ERROR_OPERATION_ABORTED result when a transfer is cancelled
#63
Conversation
This file contains 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
Seen on Windows 10 while shutting down a bulk Queue.
martinling
force-pushed
the
error-operation-aborted
branch
from
527373e to
d42ad06
Compare
|
Thanks! Opened #64 for the |
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.
This result can be seen on Windows 10 while shutting down a bulk Queue (I was stopping capture in Packetry).
I believe it should be mapped to
TransferError::Cancelled, and everything works as expected when I do so. This is also how it's handled in libusb.Since the error code was irreversibly mapped to
TransferError::Unknown, it required patching nusb to find out what happened.Perhaps
TransferError::Unknownshould have a field to retain an unexpected error code?