WiFiSetupPage never showed networks and could not be exited once entered.
Several compounding bugs were responsible across network.go and page.go.
Primary bugs fixed:
- WiFiSetupPage.Init() never assigned p.wifiDevice after FindDevices(),
so startScan() always hit the nil guard and exited without launching
a scan goroutine. No networks ever appeared in the list. A value copy
of the Wi-Fi device is now taken from m.Devices immediately after
FindDevices() returns, with an explicit error if no adapter is found.
- CheckInternetConnection() called FindDevices() on every tick, rebuilding
m.Devices every 2 seconds. This caused [NET-030] log spam, invalidated
any pointers held into the slice, and meant checkState()'s fresh Manager
instances (which have an empty Devices slice) would never detect internet
after Fix 2 was applied. CheckInternetConnection() now calls FindDevices()
only when m.Devices is empty (fresh Manager), and does a cheaper per-device
State property refresh when devices are already known (long-lived Manager).
This satisfies both callers correctly.
- Connect() called WaitForInternet(30s, 5s) synchronously before returning,
blocking the main UI thread for up to 35 seconds. It also returned an error
if internet wasn't stable in time, even though AddAndActivateConnection had
succeeded, causing the page to show "Failed to initiate connection" while NM
was still negotiating in the background. WaitForInternet removed from
Connect(); the page's existing checkConnectionStatusLoop and
handleConnectionStatusUpdate already handle post-connection state tracking.
Additional bugs fixed:
- startScan() launched a new StartScan goroutine on every R-press without
signalling the previous one to stop. Concurrent goroutines raced on
resultsChan and accumulated indefinitely. stopScan is now closed and
replaced before each scan, and checkConnectionStatusLoop is restarted
with the new channel.
- Connect() always generated a new UUID and called AddAndActivateConnection
without checking for an existing profile. Repeated connection attempts
(e.g. wrong password then correct) accumulated duplicate stale profiles
in NetworkManager. Existing profiles matching the SSID are now deleted
via Settings.Connection.Delete before creating a new one.
- m.Devices was read and written concurrently from StartScan and
CheckInternetConnection goroutines without synchronisation. A sync.RWMutex
is added to Manager; state refreshes take a write lock, StartScan device
lookup takes a read lock.
- Connect() checked wifiDevice.State using the caller's value copy taken at
Init() time, which never updated. The current state is now read from
m.Devices under lock at the point of connection.
- auth-alg: "open" was unconditionally set in the 802-11-wireless-security
settings block. This field is only meaningful for WPA/WPA2-Personal and
should be omitted for SAE (WPA3) and EAP variants. It is now only set
when KeyMgmt is "wpa-psk".
- Downloads all audio files in the background
- Tracks overall progress of audio downloads, keeping "position" when
returning
- Scroller dynamically switches between audio tracks based on the
solfeggio frequency of the currently playing proclamations
- Removed audio tracks list from Audio Options page
- Honestly a whole host of other stuff I forgot to mention
When connecting to the internet for the first time, the proclamations table is empty.
If the user navigates to Settings -> Proclamations, then the sync.SyncProclamations
function is called. After this function returns, the ProclamationOptions screen
queries the database for proclamations which returns an empty list. Even though
the database was updated, the ProclamationOptions screen's instance of the database
connection was returning empty.
Proclamations are now inserted 10 times, and in between each proclamation, the Universal Wellness proclamation is inserted.
Now I need to optimize the loop & remove the Universal Wellbeing option from the Proclamations menu (hide it) because it's always enabled.
Updated Sync functions to perform proper synchronizations instead of pure downloads.
This means that if something is deleted on the server, it will be deleted on the client as well, instead of just left hanging.
The SyncProclamations function was also updated to perform this way, but while retaining the user's saved list.
Search works well enough. Right now, you can only search via a single keyword at a time, and the search only filters based on the name, not the content. I believe we should implement a search tag feature on proclamations
Moved selection keybinds:
- Enter now saves
- Space selects
- Removed A
Updated colors to be more readable and colorblind friendly.
Cleaned up instructional text to be easier and more simple to read.
NeilClack