-
-
Notifications
You must be signed in to change notification settings - Fork 2
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
feat: handle stale BLEDevices when an adapter goes offline #21
Merged
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
- We will try to freshen the device from the global BlueZ manager. If anything goes wrong we will use the potentially stale BLEDevice since we are not using a public api (there is no public api for this)
- We will try to freshen the device from the global BlueZ manager. If anything goes wrong we will use the potentially stale BLEDevice since we are not using a public api (there is no public api for this)
- We will try to freshen the device from the global BlueZ manager. If anything goes wrong we will use the potentially stale BLEDevice since we are not using a public api (there is no public api for this)
- We will try to freshen the device from the global BlueZ manager. If anything goes wrong we will use the potentially stale BLEDevice since we are not using a public api (there is no public api for this)
- We will try to freshen the device from the global BlueZ manager. If anything goes wrong we will use the potentially stale BLEDevice since we are not using a public api (there is no public api for this)
- We will try to freshen the device from the global BlueZ manager. If anything goes wrong we will use the potentially stale BLEDevice since we are not using a public api (there is no public api for this)
- We will try to freshen the device from the global BlueZ manager. If anything goes wrong we will use the potentially stale BLEDevice since we are not using a public api (there is no public api for this)
- We will try to freshen the device from the global BlueZ manager. If anything goes wrong we will use the potentially stale BLEDevice since we are not using a public api (there is no public api for this)
- We will try to freshen the device from the global BlueZ manager. If anything goes wrong we will use the potentially stale BLEDevice since we are not using a public api (there is no public api for this)
- We will try to freshen the device from the global BlueZ manager. If anything goes wrong we will use the potentially stale BLEDevice since we are not using a public api (there is no public api for this)
- We will try to freshen the device from the global BlueZ manager. If anything goes wrong we will use the potentially stale BLEDevice since we are not using a public api (there is no public api for this)
- We will try to freshen the device from the global BlueZ manager. If anything goes wrong we will use the potentially stale BLEDevice since we are not using a public api (there is no public api for this)
- We will try to freshen the device from the global BlueZ manager. If anything goes wrong we will use the potentially stale BLEDevice since we are not using a public api (there is no public api for this)
- We will try to freshen the device from the global BlueZ manager. If anything goes wrong we will use the potentially stale BLEDevice since we are not using a public api (there is no public api for this)
Codecov Report
@@ Coverage Diff @@
## main #21 +/- ##
==========================================
- Coverage 96.24% 93.71% -2.53%
==========================================
Files 1 1
Lines 133 175 +42
Branches 25 36 +11
==========================================
+ Hits 128 164 +36
- Misses 5 10 +5
- Partials 0 1 +1
Help us with your feedback. Take ten seconds to tell us how you rate us. Have a feature suggestion? Share it here. |
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.
the global BlueZ manager. If anything goes
wrong we will use the potentially stale BLEDevice
since we are not using a public api (there
is no public api for this)