| commit | 63b2de350750d1a1ad61598f6a75ab735505d098 | [log] [tgz] |
|---|---|---|
| author | James Tucker <raggi@fuchsia.infra.roller.google.com> | Mon Aug 23 18:57:50 2021 +0000 |
| committer | Copybara-Service <copybara-worker@google.com> | Mon Aug 23 11:59:18 2021 -0700 |
| tree | f80c481916f817c8455c478f6c1fd100696fb41d | |
| parent | ab9d02f90d800a8660689214ff467ee7ee75d4d9 [diff] |
[roll] Roll fuchsia [ffx] avoid rcs -> manual target state transtions RCS states are somewhat precious, as they carry the fixed notion that a target has an Overnet Peer ID, and they will not be re-observed until Overnet observes the peer leaving the mesh and returning, which would only occur if all possible transport routes are lost. State management of targets is still spread across the code base in too many places, but this takes another step to centralize the transition graph into update_connection_state. A follow up change would do well to drop the closure from update_connection_state, that would remove the remaining cases of distributed state graph design. Original-Fixed: 83145 Original-Reviewed-on: https://fuchsia-review.googlesource.com/c/fuchsia/+/572057 Original-Revision: 4db934b023949af209e4d62a93a3aafa9dc91045 GitOrigin-RevId: 4de0442a0cdd7fd4ea3a4f106435480aba471d4f Change-Id: I39291f4c9a27987da479a92b61465f22c85c9bd4
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.