Repository navigation
feat(network): sequence bounded Wi-Fi scans (NET-05) - #548
Merged
Merged
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
Advances NET-05 with an event-loop-independent lifecycle controller for the nonblocking scan client merged in #547.
Dependency and scope
mainat765f2038b7d63e61d6db8bab1a70ce750a07d088Validation
BloomShellWifiUi*tests passed-Wall -Wextra -Werrorgit diff --checkpassedThe affected Bloom Shell ARM build is delegated to remote CI because the pinned image is not locally cached and C: remains below the 60 GiB free-space gate.
Device evidence
None claimed. This branch has no runtime consumer and cannot initiate a device scan. The online Mini Plus remained untouched on its known-good signed baseline: no SSH command, scan, profile/connection transition, Wi-Fi toggle, listener/key mutation, deployment, update, or reboot occurred. Remote CI is not physical certification.
Safety and limitations
Storage hygiene
Reused the single D:-based implementation worktree/build workspace. Created no clone, worktree, image, volume, or persistent container. Temporary shell containers used the pinned image with
--rm; no local ARM image was pulled while C: was below the gate.Remote CI result
All required checks passed on commit
3865ae329c92769dbe48753f6ec1bd8b00b88e11: