[roll] Roll fuchsia [fuchsia-async] Add close operation to Scope

This is needed in archivist and inspect and probably other places for
handling system shutdown and test scenarios. The basic use case is if
you need to begin graceful shutdown and expect the tasks in your scope
to follow suit because of some coordination happening externally.

Original-Bug: 339724492
Original-Reviewed-on: https://fuchsia-review.googlesource.com/c/fuchsia/+/1154862
Original-Revision: 0215619f537c67de115717443a28736f4cdfb647
GitOrigin-RevId: 0295e7cbac0fa616d3c98b138fe86ad1557c6888
Change-Id: I23b153a2c6ab87fb6b84ec4c3afc893adafc2394
1 file changed
tree: 388b2e122b28d54a5477f333f3f4c24c5aa61124
  1. ctf/
  2. git-hooks/
  3. infra/
  4. third_party/
  5. cts
  6. firmware
  7. flower
  8. jiri.lock
  9. MILESTONE
  10. minimal
  11. prebuilts
  12. README.md
  13. stem
  14. test_durations
  15. 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 in one of the communication channels documented at get involved.

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.