[roll] Roll fuchsia [bt][a2dp] Fix peers racing discovery to streaming

When we attempt to start streaming, the discovery and capability
collection process can take long enough that the peer starts
their own connection process after we have started collecting.

Previously we would attempt to start streaming and fail in this case,
after this change we will not attempt to start.

Original-Bug: 67408
Test: added streaming_start_configure_while_discovery

Original-Reviewed-on: https://fuchsia-review.googlesource.com/c/fuchsia/+/480219
Original-Revision: 38b29c1085ae54597c721c262ea6bd95d9a00360
GitOrigin-RevId: 65ca78da1424e320c1e7202778cbe70eb30f933a
Change-Id: I87a45c7923cd5df1fc03b60ab7ca4ac1714068cc
1 file changed
tree: a3d9b6e7c0f6257828d57ec8b4ffaed2eb5d5563
  1. garnet/
  2. infra/
  3. peridot/
  4. third_party/
  5. topaz/
  6. zircon/
  7. flower
  8. jiri.lock
  9. minimal
  10. prebuilts
  11. README.md
  12. stem
  13. test_durations
README.md

Integration

This repository contains Fuchsia's Global Integration manifest files.

Making changes

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.

Obtaining the source

First install Jiri.

Next run:

$ jiri init
$ jiri import minimal https://fuchsia.googlesource.com/integration
$ jiri update

Third party

Third party projects should have their own subdirectory in ./third_party.