[roll] Roll fuchsia [wlan] Refactor how DeviceMonitor server could exit on error The match statement within the loop that serves the DeviceMonitor protocol no longer exits on an error returned from the match. Rather, each match arm may cause an exit on error itself (or not). In particular, this makes using a continue statement more obviously correct since the match statement now returns the unit type instead of a Result. Test: This refactor does not change server behavior Original-Bug: 381233511 Original-Reviewed-on: https://fuchsia-review.googlesource.com/c/fuchsia/+/1166937 Original-Revision: 2c896e6e6f2ab30be4d1f14095063fd0f84aa0e2 GitOrigin-RevId: b29b6b6f35cad1d360cebc996daf509d811f974c Change-Id: I6abc5e577620a3f7798fa6e1473fc874a39dcf77
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.