[roll] Roll fuchsia [bt][hfp-hf] Clear stale FIDL responders before reconnection When a FIDL client disconnects and immediately reconnects to the HandsFree protocol, any outstanding WatchPeerConnected hanging-get responders from the dead client connection remain enqueued in the OneToOneMatcher queue. When a remote AG peer subsequently connects, HFP matches the peer event with a stale responder from the dead client, resulting in a transmission failure. The new FIDL client never receives the peer connection event. Clear any enqueued FIDL responders from the Hanging-Get matcher whenever a new FIDL client connects. Since the component maintains an invariant that there can only be one active FIDL connection, if the previous one is closed, then we can safely drop any outstanding responder. On the termination of an existing FIDL client connection, clear any enqueued FIDL responders to avoid storing stale state. Original-Original-Bug: 513264864 Test: fx test bt-hfp-hands-free-tests Test: Manual, fx ota, bt-hfp-hf-tool, connect peer Original-Original-Reviewed-on: https://fuchsia-review.googlesource.com/c/fuchsia/+/1612648 Original-Original-Revision: a135564f85867eeca06d1b99360c31447f2a73ff GitOrigin-RevId: 56a58961d98ec3eea782ebba05e5fd8b8ea34998 Change-Id: I2a6094bb1bb1500248f93f749890e1babf001e41
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 in one of the communication channels documented at get involved.
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.