[roll] Roll fuchsia [component_manager] Fix shutdown panic bug

It's possible to cause shutdown to panic by constructing a cycle with
dynamic offers. Specifically, this is possible if there is a service
offer from a collection, followed by a chain of dynamic offers that
routes back to this collection.

To make this impossible, detect these cycles at component creation time.

Original-Fixed: 297403341
Original-Reviewed-on: https://fuchsia-review.googlesource.com/c/fuchsia/+/1030252
Original-Revision: 9439d55d466bb0354bdfcfa704ce9399a8de0959
GitOrigin-RevId: 5f42b4dbd7821e5ad6c4be99f6e9e442590a9478
Change-Id: Ic9fdc8872b35e4ecb96eb79f739ce387f3d4a1dd
1 file changed
tree: c71588e1e712c8e9cb2bee59e56d848931999403
  1. ctf/
  2. git-hooks/
  3. infra/
  4. third_party/
  5. cts
  6. firmware
  7. flower
  8. jiri.lock
  9. MILESTONE
  10. minimal
  11. prebuilts
  12. README.md
  13. stem
  14. test_durations
  15. toolchain
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.