[roll] Roll fuchsia [cm] Store fasync::Task instead of an Abortable for dir-waiter Directory waiter futures are wrapped in an abortable before running on a detached fasync::Task. The abortable is stored in IncomingNamespace and is aborted explicitly when IncomingNamespace is dropped. When a task is dropped, its future is no longer polled by the executor. Instead of using an abortable, run the waiter in an fasync::Task directly and store that task in the IncomingNamespace. Test: fx test component_manager_tests Original-Reviewed-on: https://fuchsia-review.googlesource.com/c/fuchsia/+/674966 Original-Revision: d7629bae500939a2b024f3e8ae1f78fd8e150bd3 GitOrigin-RevId: 1524d9591fe12f8d3bd778b4e3ce6687982924a8 Change-Id: I4a751910c11bda40e5373eed5ce07fde9cff543c
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.