[roll] Roll fuchsia [starnix] Create NMFS manager framework

Move the logic from the filesystem into the Manager and perform the same
initial checks to set a framework for the calls made to the socketproxy.
Add data tracking to determine how many events are handled by the
Manager and how many (will be) sent to the socket proxy.

In the next CL, the socketproxy will be tied in and each call, set
default/add/update/remove, will call an inner function that communicates
with the socketproxy.

Added inspect logs for Manager endpoints and confirmed the node shows up
in `ffx inspect`.

Tested: manual tests, unit tests with socket proxy absent, fx test
starnix-tests --test-filter=*nmfs*

Original-Bug: 339290072
Original-Bug: 348642138
Original-Bug: 339448114

Original-Reviewed-on: https://fuchsia-review.googlesource.com/c/fuchsia/+/1058654
Original-Revision: c847bd53535e5a714497a409180e6254fceac2b0
GitOrigin-RevId: c4f55bb45f5c4521a2c4370061de8a9f2d3852f3
Change-Id: Ia589b98278c15e716954406e530d59e6b4780979
1 file changed
tree: 868af8d17acabb5a04f95241558e06fe43be56fc
  1. ctf/
  2. git-hooks/
  3. infra/
  4. third_party/
  5. cts
  6. firmware
  7. flower
  8. jiri.lock
  9. MILESTONE
  10. minimal
  11. prebuilts
  12. README.md
  13. stem
  14. test_durations
  15. 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.