Error and traceback "Task exception wasn't retrieved" with uasyncio v2 on MicroPython 1.19.1 #9965
Unanswered
jamesquilty
asked this question in
Libraries & Drivers
Replies: 0 comments
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
-
Hi everyone, I'm hoping that someone will be able to help with a uasyncio v2 (
fast_io 0.26
) error I received when trying to run my existing code on MicroPython 1.19.1 (nightly). An async function will executeraise RuntimeError(...)
when there's a problem and on 1.19.1 that causes the following to be printed to the console:and execution to halt without returning to the REPL, i.e. the ESP32 hangs, requiring manual intervention (Ctrl-C).
I'm rather confused that an error + traceback are thrown on 1.19.1 when the code functions as intended on 1.14: no traceback and the
RuntimeError
is passed up the call chain tomain.py
where it's caught by an except clause, logged, and execution resumes.Perhaps there's a clue at the top of the traceback where it states
File "uasyncio/core.py", ...
because the v2fast_io
file should besrc/lib/uasyncio/core.py
, similar tosrc/lib/asyn.py
in the traceback? Preferring modules in the filesystem over frozen bytecode is set in the very first lines ofmain.py
by changing the module search path:Can someone tell me whether my guess is indeed the source of the error... and, if so, how to make MicroPython 1.19.1 use the v2
fast_io
modulesrc/lib/uasyncio/core.py
instead of the built-in v3 version?[I'm happy to post the relevant code, I just didn't want to complicate the initial post with potential irrelevancies.]
Beta Was this translation helpful? Give feedback.
All reactions