bluetooth: Separate ConnectErrorCode |
||||||
Issue descriptionConnectErrorCode[1], used by Connect, Pair and CreateGattConnection, is the union of BlueZ's Connect[2] and Pair[3] errors. This forces users of CreateGattConnection and Connect to handle errors they will never see i.e. Pairing errors and vice versa, users of Pair need to handle errors they will never see. We should either: - Split ConnectErrorCode into PairingErrorCode and ConnectErrorCode, or - Introduce GATTConnectionError for CreateGattConnection. [1] https://cs.chromium.org/chromium/src/device/bluetooth/bluetooth_device.h?sq=package:chromium&dr=CSs&l=77 [2] https://git.kernel.org/pub/scm/bluetooth/bluez.git/tree/doc/device-api.txt#n38 [3] https://git.kernel.org/pub/scm/bluetooth/bluez.git/tree/doc/device-api.txt#n102
,
Jun 16 2017
Ed, here's a Bluetooth one you could look at.
,
Jul 5 2017
,
Jul 6
This issue has been Available for over a year. If it's no longer important or seems unlikely to be fixed, please consider closing it out. If it is important, please re-triage the issue. Sorry for the inconvenience if the bug really should have been left as Available. For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot
,
Jul 11
ecgh@, are you still interested in fixing this issue. If not please remove yourself as owner and change the status to Available.
,
Jul 12
|
||||||
►
Sign in to add a comment |
||||||
Comment 1 by ortuno@chromium.org
, May 11 2017