You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
MacBook Pro Apple M2 13.4.1 (22F82)
JupyterLab Desktop 4.0.2-1
After restart the kernel, there is a high probability that cells with only comments will get stuck while running. This situation would not happen if i just connect the kernel. However, if i restart the kernek, i execute the cells with only comments, it got stuck.
The text was updated successfully, but these errors were encountered:
Thank you for opening your first issue in this project! Engagement like this is essential for open source projects! 🤗
If you haven't done so already, check out Jupyter's Code of Conduct. Also, please try to follow the issue template as it helps other other community members to contribute more effectively.
You can meet the other Jovyans by joining our Discourse forum. There is also an intro thread there where you can stop by and say Hi! 👋
Which kernel are you using? Does the problem recur with any other kernels? Do you see the same behavior if you run the same notebook in IPython on the command line on your computer?
@Shi-YuZhang Thanks for your follow up! I'm going to close this issue, but you might want to open one against the variable inspector extension, or see if someone else has already done so.
MacBook Pro Apple M2 13.4.1 (22F82)
JupyterLab Desktop 4.0.2-1
After restart the kernel, there is a high probability that cells with only comments will get stuck while running. This situation would not happen if i just connect the kernel. However, if i restart the kernek, i execute the cells with only comments, it got stuck.
The text was updated successfully, but these errors were encountered: