[roll] Roll fuchsia [realm_builder] Server side nested component manager At ToT, the RealmBuilder nested component manager API is implemented client side. This has the following limitations: - Supports rust only. - A subrealm cannot be wrapped in nested component manager, only the root realm. There is no feasible way to implement this client side. See reboot_on_terminate in this patch for an example use case. - Adds complexity to the client library, and dislocates this feature from the rest of the RealmBuilder business logic. Cleanup: Now that reboot_on_terminate nests component manager in a subrealm, the default passthrough behavior is now sufficient and we can remove the exemption option. (Before, it would have created a conflict between the default `use from parent` passthrough and the custom `use from #trigger`.) Original-Fixed: 376072775 Original-Reviewed-on: https://fuchsia-review.googlesource.com/c/fuchsia/+/1162176 Original-Revision: a60cfa6c76c9b09f9f6a5865be7675558aa0be01 GitOrigin-RevId: 05f8845a20e90d15e6be7be251679dce1b9f16b6 Change-Id: Ib1b2e454c5fd6fa03f8c056e0b739a5ba9ac5a06
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.