[roll] Roll fuchsia [ffx][log] Fix disconnect/reconnect loops.

The strategy here is that upon receiving a disconnect from the backend,
we first check to see if there is a log entry present following the
disconnect event. If there is, we just output the disconnect event and
keep going without triggering a retry loop. This prevents cycles of
disconnect/reconnect triggered by a single disconnection.

Original-Fixed: 73714
Original-Reviewed-on: https://fuchsia-review.googlesource.com/c/fuchsia/+/581343
Original-Revision: 548c12cfbd0fcc2b307f33bc3346222106300473
GitOrigin-RevId: cc7541ff6ee601923415d19b9d649edef1c8573f
Change-Id: I9d9c0e1c8c8d104db1d8b1cbd48027e587b33205
1 file changed
tree: d04cdc94fc2e850f2fea741e6428f4ee4b947155
  1. garnet/
  2. infra/
  3. peridot/
  4. third_party/
  5. topaz/
  6. zircon/
  7. firmware
  8. flower
  9. jiri.lock
  10. minimal
  11. prebuilts
  12. README.md
  13. stem
  14. 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 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.