[roll] Roll fuchsia [bt][gap] Handle Connection Failed to be Established error When interrogation commands fail with status "Connection Failed to be Established", do not notify request callbacks. Instead, wait for the connection complete event. When the controller sends a connection complete event with status "Connection Failed to be Established", retry the connection attempt twice before giving up. Always send the Read Remote Version command when performing LE interrogation as a test of whether the connection was *actually* established successfully. A Connection Complete event with success status does not always mean that the connection was successfully established. Original-Fixed: 60412, 60517 Test: in bt-host-unittests GAP_LowEnergyConnectionManagerTest.ConnectionFailedToBeEstablishedRetriesAndSucceeds GAP_LowEnergyConnectionManagerTest.ConnectionFailedToBeEstablishedRetriesTwiceAndFails GAP_LowEnergyConnectionManagerTest.PeerDisconnectBeforeInterrogationCompletes Original-Reviewed-on: https://fuchsia-review.googlesource.com/c/fuchsia/+/460879 Original-Revision: f3c190600fe058e71c5f594a6bc5cf8339dd938d GitOrigin-RevId: 43cecea5f1ed51c5433e6034842b30f118561d85 Change-Id: I56c533daa5d66f47c1e07ef404970f96f919433d
This repository contains Fuchsia's Global Integration manifest files.
All changes should be made to the internal version of this repository. Our infrastructure automatically updates this version when the internal one changes.
Currently all changes must be made by a Google employee. Non-Google employees wishing to make a change can ask for assistance via the IRC channel #fuchsia on Freenode.
First install Jiri.
Next run:
$ jiri init $ jiri import minimal https://fuchsia.googlesource.com/integration $ jiri update
Third party projects should have their own subdirectory in ./third_party.