[roll] Roll fuchsia [component_manager] upgrade component for duration of storage admin

Instead of upgrading the component reference when needed, the storage
admin should upgrade the reference once when initialized and hold the
upgraded reference for the duration of the connection. This ensures that
the component reference will remain valid, and the storage admin
protocol will thus be less fragile.

Also reverts recent changes to the
fuchsia.sys2.StorageAdmin/OpenComponentStorageById function, which
caused some test failures.

Original-Bug: 498441399
Original-Reviewed-on: https://fuchsia-review.googlesource.com/c/fuchsia/+/1561833
Original-Revision: a346a259aa653e896b67cce9ffd7479fd5109f6d
GitOrigin-RevId: dda9f373b18109a41a94404105aa75920f1d3861
Change-Id: Ic132c72ea12dab55b65a717b0590c97aad9a8680
1 file changed
tree: 84fa8dccb96b36490241ab3b765fcbaa9ad425c9
  1. ctf/
  2. git-hooks/
  3. infra/
  4. third_party/
  5. cobalt
  6. flower
  7. jiri.lock
  8. MILESTONE
  9. minimal
  10. prebuilts
  11. README.md
  12. stem
  13. test_durations
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.