Address a potential issue in the PybricksHubUSB.write_gatt_char method
#109
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.
Previously, there was a concern that this part of the code could get stuck if the USB hub disconnected or didn't send a response.
Here's how I've addressed it:
If the hub disconnects, a
RuntimeErrorwill occur. If the operation times out, anasyncio.TimeoutErrorwill occur.I've also included some checks in
tests/connections/test_pybricks.pyto ensure this new behavior works as expected in both disconnection and timeout situations.