[roll] Roll fuchsia [wlanix] Populate associated status in scan result

Upstream checks the BSS status in scan results to determine whether a
BSS is associated before it performs a signal poll. If it deems that the
BSS is not associated, it skips the signal poll entirely. As a result,
the client state machine in upstream may disconnect the network due to
low RSSI (because the network is reported with the default -127 RSSI).

Original-Bug: 473850388
Test: Verified connection persisted and that log no longer output error
about signal poll

Original-Reviewed-on: https://fuchsia-review.googlesource.com/c/fuchsia/+/1470060
Original-Revision: 4ab08ca5f6af801a416582e87bbd2a9937c74eb1
GitOrigin-RevId: de701ea6a496d3297b42a1fe76e0a23fa9e413b7
Change-Id: I17b604347e8f8e04e8cb60f630d74faa7ae7b6d5
1 file changed
tree: 1bc3390042d934c95086c627879f315b77f71819
  1. ctf/
  2. git-hooks/
  3. infra/
  4. third_party/
  5. flower
  6. jiri.lock
  7. MILESTONE
  8. minimal
  9. prebuilts
  10. README.md
  11. stem
  12. 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.