This repository has been archived by the owner on Mar 6, 2024. It is now read-only.
-
-
Notifications
You must be signed in to change notification settings - Fork 79
After apply()
and asyncio.run()
, Jupyter kernel cannot execute any code
#87
Comments
Chaoses-Ib
added a commit
to Chaoses-Ib/ComfyScript
that referenced
this issue
Jan 7, 2024
Chaoses-Ib
added a commit
to Chaoses-Ib/ComfyScript
that referenced
this issue
Jan 7, 2024
Chaoses-Ib
added a commit
to Chaoses-Ib/ComfyScript
that referenced
this issue
Jan 7, 2024
The above example code runs fine for me on Jupyter notebook, Jupyter lab en VSCode. This is with Python 3.12.1 and the latest relevant packages.
|
I created an env with Python 3.12.1 and the packages you listed. The problem can still be reproduced on Jupyter Notebook, Jupyter Lab and VS Code.
|
What's your OS? |
Windows 11 23H2 (22631.2861). Just tried, in my WSL2 there is no such problem. Maybe I should just stop using Windows... |
I found someone who had the exact same problem as me, although it was about three years ago: winpython/winpython#950 |
It will be a long while before I can test this on Windows. |
👍Upgraded to v1.5.9 and now it's working fine. |
Chaoses-Ib
added a commit
to Chaoses-Ib/ComfyScript
that referenced
this issue
Jan 15, 2024
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Before I call
nest_asyncio.apply()
, the notebook works fine. However, after I callapply()
andasyncio.run()
, the notebook cannot execute any cells and will block forever.I've tested this on Python 3.9 and Python 3.12, the official Jupyter Notebook and VS Code's Jupyter Notebook extension, all have this problem. But just a few days ago there was no problem. I'm not sure what happened.
Example
Packages
The text was updated successfully, but these errors were encountered: