Jupyter notebook cell instruction after asyncio.run is not executing with 6.28.0v of ipykernel
Nobody has claimed this yet.
Assessment
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Newbie friendliness
- 25/100
Research direction
Reproduce the reported sequence in a Jupyter notebook on Windows with Python 3.9.2 and ipykernel 6.28.0, checking whether a cell after asyncio.run() completes. Start by reviewing the ProactorEventLoop change in PR 1184 and compare behavior before and after that release. Done means subsequent notebook cells execute normally after asyncio.run().
Written by the indexing model from the issue text.
Description
With the latest version of ipykernel 6.28.0v, jupyter notebook cell after the asyncio.run() is not completing its execution.
I'm running it on Windows and ProactorEventLoop was enabled on Windows for ipykernel here in the latest version.
The Python version I'm using is 3.9.2 and
Package Version
matplotlib-inline 0.1.6
psutil 5.9.7
nest-asyncio 1.5.8
tornado 6.4
traitlets 5.14.1
packaging 23.2
jupyter_core 5.7.1
ipython 8.18.1
comm 0.2.1
debugpy 1.8.0
jupyter_client 8.6.0
pyzmq 25.1.2
qtconsole 5.5.1
jupyter 1.0.0
jupyter-console 6.6.3
jupyterlab 4.0.10
Can someone please help me out here?
- Dominant language
- Python
- Stars
- 734
- Forks
- 411
- Avg merge
- 1d 2h
- Merged PRs (30d)
- 9
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from ipython/ipykernel
-
Difficulty 1/5 Under an hour Newbie friendliness 72/100
-
Difficulty 4/5 3-5 days Newbie friendliness 48/100
-
Difficulty 4/5 3-5 days Newbie friendliness 68/100
-
ipython/ipykernel#1550 · 1 comment · 1 reaction · 1 assignee ·
-
Difficulty 3/5 1-2 days Newbie friendliness 66/100
All issues in ipython/ipykernel
Similar issues
-
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
syfoud/Simulated_Scepter#172 ·
-
A cancelled tests run makes the coverage comment workflow fail and reports it as a red check on main Openarea: ci bug perceived difficulty: 3
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
Nitjsefnie-Harness-Commons/daedalus#921 · 1 comment ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 86/100
EleutherAI/lm-evaluation-harness#4207 ·
-
Difficulty 1/5 Under an hour Newbie friendliness 92/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
ClickHouse/clickhouse-connect#1057 ·