[roll] Roll fuchsia [ffx] Make ffx config read-only This change refactors `EnvironmentContext` to hold a read-only `Config` object loaded at initialization, removing the need for a read-write lock and cache invalidation. Modification methods (`set`, `add`, `remove`) are removed from `ConfigQuery` and moved directly to the plugins that need to modify config files on disk (`ffx config`, `ffx sdk`, `ffx repository default`). Tests that need to modify configuration now use `TestEnvBuilder` to set up overrides before building the environment, ensuring the configuration remains read-only after creation. Fixed a bug in `EnvironmentContext::strict` where it failed to populate `config.runtime` with `runtime_args`. Disabled discovery in `test_auto_reconnect` to avoid timeouts in isolated test environments. Test: All affected tests passed. `fx build` successful. Original-Original-Bug: 342038349 Original-Original-Reviewed-on: https://fuchsia-review.googlesource.com/c/fuchsia/+/1604795 Original-Original-Revision: c4e2096a7ba52d6d63257aa0fd875b5894723794 GitOrigin-RevId: d972ab69533d2425e7016b23a079277057380ad2 Change-Id: Ia7e9056063ff7921c69a76a145388dbae9de765c
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 in one of the communication channels documented at get involved.
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.