search

ivmarkov / rust-esp32-std-demo

Rust on ESP32 STD demo app. A demo STD binary crate for the ESP32[XX] and ESP-IDF, which connects to WiFi, Ethernet, drives a small HTTP server and draws on a LED screen.
Apache License 2.0
784 stars 105 forks source link

VSCode and WSL go crazy when running the example #98

Closed Squirrelcoding closed 2 years ago

Squirrelcoding commented 2 years ago

Ok, this issue is quite weird. I'm not sure if its a problem with my computer or the code, but when I run the example in WSL inside of VSCode, this happens:

Steps to reproduce (assuming everything is installed)

Everything is fine until I (13509) rust_esp32_std_demo: About to open a TCP connection to 1.1.1.1 port 80 is printed out, and everything goes downhill... It seems as if espmonitor freezes on this line of code! I was wondering two things:

A response would be helpful!

Edit: Heres a screenshot of something similar to what's happening, right here its an HTTP request. Screenshot (106)

ivmarkov commented 2 years ago

And what happens when you comment out that line of code?

Squirrelcoding commented 2 years ago

@ivmarkov if I comment out test_tcp(), the next function to freeze is test_mqtt_client(), and it freezes right before connecting.

I was playing around with the demo as I was writing this, and shut down my PCs hotspot while the serial monitor was still running, and a couple things happened:

I suspect that the issue is that the logs aren't being outputted for whatever reason.

After more investigating while writing this, I used putty to run the demo, and pretty much everything else works. It turns out the issue with WSL going crazy and all are related to WSL and Windows hotspot having trouble running at the same time, which is a known issue.

edit: oops I didnt mean to comment as I was writing this, I accidentally typed ctrl + enter thinking it would create a new line like in VSCode!

Squirrelcoding commented 2 years ago

The issue is NOT with the demo, its the fact that running WSL and a hotspot at the same time in Windows is causing issues, which is already a known issue with WSL, so I'm going to go ahead and close this.