[roll] Roll fuchsia [component_manager] actions don't need to ensure Discover runs first When `ResolvedInstanceState::new` populates the `children` hashmap with newly created components, the function discovers each child before returning. This means that all children are discovered before the instance state mutex of the parent component is released, ensuring that all static children are discovered before it's possible to get a reference to them. Unfortunately this wasn't true for dynamic children or the root component. This commit rearranges the codepath for adding dynamic children such that dynamic children are discovered before references to them become accessible, along with the codepath by which the component model is started to ensure that the root component is discovered before capabilities accessible through component manager's out directory start running. With these changes action implementations do not need to be careful about ensuring that they wait for a discover action to run, as it's safe to assume that if a reference can be obtained to a component then the component has been discovered. Multiply: namespace-capabilities-integration-test Multiply: controller_integration_test Multiply: stop_with_escrow_integration_test Original-Reviewed-on: https://fuchsia-review.googlesource.com/c/fuchsia/+/1042093 Original-Revision: 2e01df88bee62bc406dfc34e7e8146ef40c2f04f GitOrigin-RevId: 2f03b669b8612f0046463e222fee8525e856f54a Change-Id: If1a7f18e31117c1028b810d79ff05b1bae98ae3e
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.