| commit | 1bfea535929332a0fc6c40fba0eed827fada5f40 | [log] [tgz] |
|---|---|---|
| author | Yegor Pomortsev <ypomortsev@fuchsia.infra.roller.google.com> | Wed Aug 16 01:10:00 2023 +0000 |
| committer | Copybara-Service <copybara-worker@google.com> | Tue Aug 15 18:11:16 2023 -0700 |
| tree | 70631c93a6e50a74187f9383af5108b25333a8b6 | |
| parent | 9d7814b23b6bcae699b3be82add65cf32d65fe0f [diff] |
[roll] Roll fuchsia [components] Create logger without going through namespace StartAction creates a logger attributed to the started component. This requires a connection to the LogSink protocol routed to the component. Previously, StartAction got a connection in a round-about way by constructing the component's namespace, finding the appropriate entry with a directory that contains LogSink, and opening the protocol through that directory. Now, StartAction issues a route request for the LogSink protocol use, without connecting through the namespace. This simplifies StartAction and removes the need to write a "connect to protocol" method in Namespace, at least for now. ELF runner still connects to LogSink in the component's namespace in the same way. Original-Bug: 131717 Original-Reviewed-on: https://fuchsia-review.googlesource.com/c/fuchsia/+/897618 Original-Revision: 9135ed9c7a916f17e544c47c27bb3a647804e239 GitOrigin-RevId: 9cbd24911f0f7737ee74dd0c73bd7c4b45a6a7f0 Change-Id: I55fb0bb6dd4ac0d6e2adb22a22ecd45e8921f2b5
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.