[roll] Roll fuchsia [network] Precise capturing on iterate_ip

While implementing a similar method for socket destruction
notifications, I learned that without the precise capturing the return
value is assumed to hold the borrow of `diagnostics`. This isn't true
and also constrains how the returned stream can be used.

Original-Reviewed-on: https://fuchsia-review.googlesource.com/c/fuchsia/+/1586290
Original-Revision: b4c6515d8c9b05b175056f061eeec74641a0957e
GitOrigin-RevId: c259498eaf5a2850021de328b9a993cee096d51b
Change-Id: I54e98cd1ddc9c7432ce2584bf1f300b0b22809b8
1 file changed
tree: 2684d33efe464d20dac5de324ccdbc505c160b7e
  1. ctf/
  2. git-hooks/
  3. infra/
  4. third_party/
  5. cobalt
  6. flower
  7. jiri.lock
  8. MILESTONE
  9. minimal
  10. prebuilts
  11. README.md
  12. stem
  13. test_durations
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 in one of the communication channels documented at get involved.

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.