Comments (6)
except asyncio.CancelledError: ... raise DeadKernelError("Kernel died")
The cause seems to be a cancelation. Can this be related to the fix for your #58 issue?
from nest_asyncio.
I don't test the combination of jupyter + cancellation -- these tests don't do cancel
- I've confirmed the error goes away if I downgrade to
1.5.1
- the context for the trace above was a
pytest
usingtestbook
, but I've confirmed that an interactive notebook fails too, it looks like right after it successfully executes the last cell
these were the only logs from jupyter:
[I 14:00:12.410 NotebookApp] Replaying 3 buffered messages
[I 14:01:28.417 NotebookApp] KernelRestarter: restarting kernel (1/5), keep random ports
kernel 59511ee4-8c2c-419f-8ba7-25f2b4d14a43 restarted
[I 14:02:04.646 NotebookApp] Saving file at /jupyter_tests.ipynb
from nest_asyncio.
this doesn't show the same issue, but it might be related:
from nest_asyncio.
I can't reproduce the error with the task being None, but there's a new v1.5.4 version out that might fix it.
from nest_asyncio.
yes, I can confirm the latest code changes address my problem. thank you!
from nest_asyncio.
OK that's great to hear.
from nest_asyncio.
Related Issues (20)
- nest_asyncio.apply() to check for asyncio.AbstractEventLoop HOT 1
- Create new event loop if there isn't one running HOT 6
- Can't patch loop of type <class 'NoneType'> HOT 2
- 1.5.2 and 1.5.3 broke some current_task detection HOT 2
- 1.5.1-1.5.4 is breaking vaex due to #61 HOT 3
- nested tasks causing deadlock? HOT 1
- Request stuck in ProcessPoolExecutor HOT 4
- feature request: unapply HOT 1
- DeprecationWarning on Python 3.10
- RuntimeError: cannot enter context: <_contextvars.Context object at %> is already entered HOT 1
- ThreadPoolExecutor issue HOT 8
- Release tag for v1.5.6 HOT 1
- Execution of Unit Tests Dead Locked After Upgrade to Python 3.10.7 HOT 3
- Lost Logs HOT 1
- nest_ayncio breaks tests under Python 3.10.9 HOT 2
- nest_asyncio.apply not working unless entire asyncio package is imported HOT 1
- strange hanging behavior with `nest_asyncio` when used in combination with `concurrent.futures `ProcessPoolExecutor` HOT 3
- RFE: is it possible to start making github releases?🤔 HOT 2
- Nested asyncio.run is parallel on first call but serial on second HOT 1
Recommend Projects
-
React
A declarative, efficient, and flexible JavaScript library for building user interfaces.
-
Vue.js
🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.
-
Typescript
TypeScript is a superset of JavaScript that compiles to clean JavaScript output.
-
TensorFlow
An Open Source Machine Learning Framework for Everyone
-
Django
The Web framework for perfectionists with deadlines.
-
Laravel
A PHP framework for web artisans
-
D3
Bring data to life with SVG, Canvas and HTML. 📊📈🎉
-
Recommend Topics
-
javascript
JavaScript (JS) is a lightweight interpreted programming language with first-class functions.
-
web
Some thing interesting about web. New door for the world.
-
server
A server is a program made to process requests and deliver data to clients.
-
Machine learning
Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.
-
Visualization
Some thing interesting about visualization, use data art
-
Game
Some thing interesting about game, make everyone happy.
Recommend Org
-
Facebook
We are working to build community through open source technology. NB: members must have two-factor auth.
-
Microsoft
Open source projects and samples from Microsoft.
-
Google
Google ❤️ Open Source for everyone.
-
Alibaba
Alibaba Open Source for everyone
-
D3
Data-Driven Documents codes.
-
Tencent
China tencent open source team.
from nest_asyncio.