[roll] Roll fuchsia [camera] Avoid a dependency loop
When camera_device_watcher is merged back, the resulting capabilities
routing introduces a dependency loop that is statically calculated.
The dependency is based on which component should be shutdown first
determined by shutting the client side of any service before the
server side.
Due to the nature of the service routing in smart_display, there is a
loop in the dependency graph. In practice, this loop has no real
consequences because all camera clients and stack components are
expected to tolerate component failures.
Making this dependency (camera_device_watcher to setui_service) "weak"
breaks that dependency loop.
Original-Bug: b/242576219
Test: Build on smart_display.sherlock and run on Sherlock + Meet.
Build on workstation.x64 and run on NUC + Meet.
Original-Reviewed-on: https://fuchsia-review.googlesource.com/c/fuchsia/+/712422
Original-Revision: fbdb8e7dd43dd21df42eeb72c76a7050172f7ce5
GitOrigin-RevId: 4355b91b9172d484753b7625aa1cdc8c09627765
Change-Id: I4b01873b47433e58e348ad72849a0aff3e43dee5
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.