-
Notifications
You must be signed in to change notification settings - Fork 115
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
Refactor BLE connecting to allow scanning for vehicle presence #353
Merged
Merged
Changes from all commits
Commits
Show all changes
6 commits
Select commit
Hold shift + click to select a range
edcf69a
Refactor BLE connecting to allow scanning for vehicle presence
Lenart12 7abc52f
Remove unnecessary goroutine for context cancellation in scanVehicleB…
Lenart12 2527064
Simplify local name check in scanVehicleBeacon function
Lenart12 3c91d3d
Do not retry BLE connecting to vehicle in certain cases
Lenart12 d724cd9
Fix MacOS deadlock during BLE scan
0231440
Fix linter error in `ble.tryToConnect`
Lenart12 File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
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
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
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
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.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Is connecting with
target.Addr()
significantly faster than scanning? If so, then it might be worth modifying the API to accepttarget.Addr()
instead oftarget
. This could allow clients to cachetarget.Addr()
to use for future connections.We'd need to consider being able to recover in cases where
target.Addr()
changes due to a VCSEC replacement, as well as detectingErrMaxConnectionsExceeded
. But optmizing for the common case could be useful.There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Good idea, but If we would count on "longer term" address caching it would make sense to also seperate this part of the
tryToConnect
method to its own function, since it adds back the same pain point this PR is trying to address. Thoughts?There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I'm fine punting that improvement to a different PR. The reason I proposed it because implementing it as part of this one would help limit API churn.