[roll] Roll fuchsia [fuchsia_async] Document socket PEER_CLOSED behavior.

Adds comments to emphasize the fact that `Socket::read*` functions
return `Ok(0)` when their peer has closed. This is very counterintuitive
from a Fuchsia standpoint, but is the behavior that the relevant Rust
traits specify.

Hopefully the comments will save some poor soul from the fate that
befell me today.

Original-Reviewed-on: https://fuchsia-review.googlesource.com/c/fuchsia/+/1235466
Original-Revision: 24c1d50b2ec83f4cf0c44350b358953c44b037fd
GitOrigin-RevId: c91e65adc8513d7ff3e0422647a7a927a48f81cf
Change-Id: I6ae14c90b9341b91b75beac1a4cd58147ad4801a
1 file changed
tree: 93e8e50f20b6e09c69eb00e15c38a4fd1963b9ce
  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 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.