[roll] Roll fuchsia [component_manager] fuchsia.sys2.Realm seralizes requests This change causes fuchsia.sys2.Realm to serialize request handling, instead of processing them in parallel. This affords a guaranteed ordering between requests, which can be useful in cases like follows: 1) Client sends CreateChild request. 2) Immediately following #1 (without waiting for a result), client sends OpenExposedDir Currently, #2 is processed in parallel with #1, so it would fail with INSTANCE_NOT_FOUND even if #1 succeeds. Sequencing these requests, although it sacrifices the opportinuity for parallelism, is more intuitive for users. Original-Reviewed-on: https://fuchsia-review.googlesource.com/c/fuchsia/+/575787 Original-Revision: ae7eeb5b7f46d01991b8575a7e813fadcb734bef GitOrigin-RevId: 331afc5b2856bb507f89d98bdd8402d6201921d2 Change-Id: Ic68a0de7fef509294835a9524366300a446ad12d
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.