-
Notifications
You must be signed in to change notification settings - Fork 78
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
uasyncio / EAGAIN #30
Comments
I'm not sure. The errors are definitely coming for modlwip sockets. I'm rebasing on the micropython upstream, so that fix is included in my tree. I believe there were more fixes to modlwip recently, the latest revision in this repo is 4dcb7d0, you may want to try build. Unfortunately, I don't have time now to look into esp8266 issues. |
Hm... interesting... I removed these two lines from boot.py to disable the AP mode - no more EAGAIN...
That means the error happens only when not in AP mode, which currently makes the AP mandatory... The ENOMEM error is still there, when doing Ctrl-C and restart run()... |
I don‘t get this. Your master branch is based on current upstream‘s master, so yes, this patch is included. What other fixes do you mean? |
Tested with raw sockets, no asyncio... same problem:
Catching EAGAIN works but this only circumvents that bug...
Seems to be an upstream problem, since this happens with micropython/master, too |
@c0d3z3r0 why you have closed this? |
@JuniorJPDJ because this is an upstream issue ;) |
Hi there,
I am having the same issue that should have been fixed in micropython/micropython#4322
Test code:
What could be wrong here?
The text was updated successfully, but these errors were encountered: