[roll] Roll fuchsia [component_debug] Manifest is encoded and sent using an iterator

The RealmQuery.GetManifest call fails for manifests that are too
large to fit in a Zircon channel.

To work around this problem, component manager will now encode
the manifest into a persistable format (per RFC-0120) and send
that data over a dedicated iterator.

We cannot use a VMO because we need to maintain compatibility
with overnet.

This change also cleans up GetAllInstances by tying the iterator
to a TaskScope and closing it when there is no more data to be sent.

Original-Fixed: 122209
Original-Reviewed-on: https://fuchsia-review.googlesource.com/c/fuchsia/+/806987
Original-Revision: cc8eabe6f9821c375595f289f8873a6b0b3e1e5d
GitOrigin-RevId: f1adbd268aa702fd7652e39ea821a6ca87443fa5
Change-Id: I9371c88fea7e3d7caaeddf40f01b96c67dbc63f5
1 file changed
tree: 8e4d5812d7c268c818e1365b85a13d8d3d3e9467
  1. git-hooks/
  2. infra/
  3. third_party/
  4. cts
  5. firmware
  6. flower
  7. jiri.lock
  8. minimal
  9. prebuilts
  10. README.md
  11. stem
  12. test_durations
  13. 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.