Issue 19: Handle open/write failures due to disappearing transports #20
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
sjlongland
force-pushed
the
bugfix/issue19-missing-device
branch
2 times, most recently
from
b74bf30
to
1fee1cb
Compare
sjlongland
force-pushed
the
bugfix/issue19-missing-device
branch
from
1fee1cb
to
1d2c2d3
Compare
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.
If the transport disappears, or fails to be created in the first place, abort and put the device into a
FAILEDstate. The process can hook thefailedsignal to detect this, and handle the event as they require.