[roll] Roll fuchsia [rcs] Support connecting to incoming namespace of core/toolbox

This change fixes a bug in remote-control which prevented the ability
of connecting to protocols in the incoming namespace of a component due
to protocols being nested under a svc directory inside the incoming
namespace.

When using OpenDirType::Namespace, the namespace directory looks as:

```
ns/
  svc/
     fuchsia.my.Protocol
  pkg/
```

So requests come for `svc/fuchsia.my.Protocol`.

Additionally this change introduces an API in the rcs library to connect
to protocols in the incoming namespace of core/toolbox.

Original-Fixed: b/304302408
Original-Reviewed-on: https://fuchsia-review.googlesource.com/c/fuchsia/+/929192
Original-Revision: 58a192552b149fe4d0b0de8649b6e56dfe6028cd
GitOrigin-RevId: a95c1b4aefd6a954e77ab0f1603ffcb309ba4ee0
Change-Id: Id6759a36917e729cfaa172ba0d67611f210fd63a
1 file changed
tree: a17025195fe696b470dc4c0a3b033a7c12bf6749
  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.