Skip to content
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
merged 19 commits into from
Aug 20, 2022

Conversation

bdraco
Copy link
Member

@bdraco bdraco commented Aug 20, 2022

  • 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)

bdraco added 19 commits August 19, 2022 12:39
- 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
Copy link

codecov bot commented Aug 20, 2022

Codecov Report

Merging #21 (78c22b1) into main (1c92f6e) will decrease coverage by 2.52%.
The diff coverage is 88.46%.

@@            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     
Impacted Files Coverage Δ
src/bleak_retry_connector/__init__.py 93.71% <88.46%> (-2.53%) ⬇️

Help us with your feedback. Take ten seconds to tell us how you rate us. Have a feature suggestion? Share it here.

@bdraco bdraco merged commit 012c94c into main Aug 20, 2022
@bdraco bdraco deleted the freshen_ble_device branch August 20, 2022 03:36
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

1 participant