nteract/papermill

RuntimeError: Kernel didn't respond in 60 seconds

Open

#776 opened on Feb 6, 2024

View on GitHubContributor guide
 (2 comments) (0 reactions) (0 assignees)Python (402 forks)batch import
bughelp wanted

Repository metrics

Stars
 (5,381 stars)
PR merge metrics
 (PR metrics pending)

Description

🐛 Bug

Hello team, I would like some help ~~

We use papermill to execute jupyter notebook, when running papermill using subprocess multiprocessing the following error occurred.

RuntimeError (\"Kernel didn't respond in %d seconds\" % timeout)\nRuntimeError: Kernel didn't respond in 60 seconds"

RuntimeError(msg)\nRuntimeError: Kernel died before replying to kernel_info"

Relevant pageages version are jupyter-core==4.9.1, jupyter-client==7.1.2, nbconvert==7.0.0, papermill==2.3.4

Contributor guide

Research direction
Investigate the kernel startup process when using subprocess multiprocessing. Look at the jupyter client kernel manager and how it handles timeouts.
Tech stack
python
Domain
backenddata
Issue type
Bug
DifficultyEstimated implementation difficulty for a new contributor, from 1 for very small changes to 5 for expert-level work.
3
Estimated timeA rough time range for an experienced contributor to investigate, implement, test, and prepare a pull request.
Half day
Activity statusHow available the issue appears right now: fresh, active, stale, blocked, or waiting on maintainer input.
Active
ClarityHow clearly the issue explains the expected change, acceptance criteria, and next step.
Needs investigation
Prerequisites
PythonGit
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
65