[wlan][sl4f] Fix locking around hanging get_update

Previously if a get_update hung from never getting an update from the
policy layer, the lock around the inner facade would still be held by
the hanging get_update even if the consumer timed out from the update.
After that, no other commands would work because they would be waiting
for the lock. Now the update listener is behind a separate lock and the
lock is behind a reference so that the lock and update stream can be
reset for each test.

Bug: 56323
Test: act.py -c <config> -tc SavedNetworksTest
	tested that only the one test fails if it never gets an update
Change-Id: I8680d0802a1186f683689ecd1f02ecfb29800b4e
Reviewed-on: https://fuchsia-review.googlesource.com/c/fuchsia/+/407639
Commit-Queue: Naomi Mccracken <nmccracken@google.com>
Reviewed-by: Kevin Sakuma <sakuma@google.com>
Reviewed-by: Joe Brennan <jmbrenna@google.com>
Testability-Review: Kevin Sakuma <sakuma@google.com>
2 files changed
tree: 94d2eb6b21fe2e7073132e98312df6562b323798
  1. .clang-format
  2. .clang-tidy
  3. .gitattributes
  4. .gitignore
  5. .gn
  6. .style.yapf
  7. AUTHORS
  8. BUILD.gn
  9. CODE_OF_CONDUCT.md
  10. CONTRIBUTING.md
  11. LICENSE
  12. OWNERS
  13. PATENTS
  14. README.md
  15. boards/
  16. build/
  17. bundles/
  18. cts/
  19. docs/
  20. examples/
  21. garnet/
  22. products/
  23. rustfmt.toml
  24. scripts/
  25. sdk/
  26. src/
  27. third_party/
  28. tools/
  29. zircon/
README.md

Fuchsia

Pink + Purple == Fuchsia (a new operating system)

What is Fuchsia?

Fuchsia is a modular, capability-based operating system. Fuchsia runs on modern 64-bit Intel and ARM processors.

Fuchsia is an open source project with a code of conduct that we expect everyone who interacts with the project to respect.

How can I build and run Fuchsia?

See Getting Started.

Where can I learn more about Fuchsia?

See fuchsia.dev.