You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I'm testing your smart.js code, and I think I found a bug in it. When I first started it up, I tried to get the WiFi status:
smartjs 12040/3456$ Wifi.status()
"�W�?"
I compiled this with the 1.2.0 SDK, and it looks like the bug originally stems from there: when the WiFi station isn't online for whatever reason, wifi_station_get_connect_status() returns -1 (well, it's an u8 so actually 255.) I'll see if I can get that fixed or documented in the SDK, but in general, maybe the select statement in v7_esp.c, Wifi_status could use a default case so it doesn't return uninitialized memory when the WiFi status value is something weird?
The text was updated successfully, but these errors were encountered:
I'm testing your smart.js code, and I think I found a bug in it. When I first started it up, I tried to get the WiFi status:
smartjs 12040/3456$ Wifi.status()
"�W�?"
I compiled this with the 1.2.0 SDK, and it looks like the bug originally stems from there: when the WiFi station isn't online for whatever reason, wifi_station_get_connect_status() returns -1 (well, it's an u8 so actually 255.) I'll see if I can get that fixed or documented in the SDK, but in general, maybe the select statement in v7_esp.c, Wifi_status could use a default case so it doesn't return uninitialized memory when the WiFi status value is something weird?
The text was updated successfully, but these errors were encountered: