[roll] Roll fuchsia [component_manager] Fix bug in event subscription

Subscribing to an event of type T coming from different scopes
under a different name is valid. The previous implementation was only
checking that the number of events that were successfully routed was
equal to the number of requested events. However, that's not correct as
renamed events are merged into a single event holding multiple scopes.

Tested: component-manager-tests

Original-Reviewed-on: https://fuchsia-review.googlesource.com/c/fuchsia/+/663064
Original-Revision: f2a921add91f7e2e35d993976aeac8d7023e226a
GitOrigin-RevId: 3b4b4d8c8969b2c428d4241c3b1721b8972b5602
Change-Id: I6a2ab7540f9ee9c56ab4bc7cdf72c118f20a8e10
1 file changed
tree: 72b027a916ff9b921d189a6478840dc187e22522
  1. infra/
  2. third_party/
  3. cts
  4. firmware
  5. flower
  6. jiri.lock
  7. minimal
  8. prebuilts
  9. README.md
  10. stem
  11. test_durations
  12. 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.