[roll] Roll fuchsia [ffx] "ffx target wait" should reresolve scope-id in loop

When waiting for a device to appear, instead of parsing the target
spec just once into an address, we should do it on every pass through
the loop. This is because parsing a target specification
string into an query includes resolving scope-ids, and those are
ephemeral. If a scope is not _currently_ found, we will store a "0"
in the ipv6 address.  This needs to be fixed (b/481735207) but meanwhile
it leads to us never finding a device specified with a scope id if that
scope-id is not available when the command is initially invoked.

The fix is to do the conversion into an address every time through the
loop. Again, this is bad, but it is a quick fix for a P1 problem, before
we can come up with the right design for turning strings with scope-ids
into ipv6 addresses.

Original-Bug: 481448915

Original-Reviewed-on: https://fuchsia-review.googlesource.com/c/fuchsia/+/1495559
Original-Revision: 80b9ee5497f44a7da39ba03cf043056f4e5fd201
GitOrigin-RevId: e346cb7ec22413ebe96a6640d191b248b162e36d
Change-Id: I3bf02f89b53505a76a70370d372956e219f3affa
1 file changed
tree: 1cc04e5b733909e9936eff602ca69e4c5c39a293
  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.