[roll] Roll fuchsia [bedrock] Function to open a bedrock capability and report errors

We now have a first instance of an error that is entirely handled in
bedrock code paths, without relying on legacy fallback. That is the Unit
capability/Void source.

This CL builds a little scaffolding so that more bedrock error handling
can be added easily in the future.

It turns out that we're not reporting errors to logs in the bedrock
paths, whereas we do in legacy routing. This CL adds error reporting as
best as possible.

Original-Reviewed-on: https://fuchsia-review.googlesource.com/c/fuchsia/+/983625
Original-Revision: 8d6a97b4086a521834f4a3a42967411bc84466db
GitOrigin-RevId: b7930656727248ffa504560976beb2f2f01cb54a
Change-Id: Ic2b2cf7c37502acc0e0096e5e03cf9ccc7cb3529
1 file changed
tree: f66f382572e0366b1517ae96dbd5dc8c2e2e2fe0
  1. git-hooks/
  2. infra/
  3. third_party/
  4. cts
  5. firmware
  6. flower
  7. jiri.lock
  8. MILESTONE
  9. minimal
  10. prebuilts
  11. README.md
  12. stem
  13. test_durations
  14. 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 via the IRC channel #fuchsia on Freenode.

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.