-
Notifications
You must be signed in to change notification settings - Fork 31
Pico W stuck in an infinite loop #44
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Comments
Ok so pico w gets stuck in an infinite loop in _send_bytes because we get an error code 32 EPIPE I've got something that fixes it for me I'll raise a PR for review. |
On the Pico W we can get in an infinite loop if we request pages too quickly. This is because we get an OSError 32 Broken Pipe back from which we can't recover. I've made it so any of the unexpected errors will be re-raised. Fixes this issue: adafruit#44
I do not own a Pico W, but from the code I see a couple of things. You set I am unable to replicate the issue with ESP32S2 TFT Feather, maybe there is something wrong with the sockets on Pico's version of CP? PS: |
The |
Tagging @jepler for interest |
As it is the send from Pico W -> Chrome I guess it could be somehow Chrome -> Pico W wifi breaks the connection and the Pico W is just genuinely reporting a Broken Pipe.... I get the same error using FireFox as well - testing in case it was a browser specific thing. |
Resolved by: #45 |
If I do the GET request too quickly on a PICO W it gets stuck in an infinite loop.
I took inspiration from this issue on how to debug: #41
When I add
print(bytes_sent, bytes_to_send)
to the response.py _send_bytes method I can see it gets stuck in an infinite loop.Hard to capture in text as the board locks up and so does Mu serial connection I took a video and I've attached an image from the point where the issue happens.
code.py at the moment is:
and index.html is:
The text was updated successfully, but these errors were encountered: