nteract/papermill

The batch script runs on pressing Ctrl +C

Open

#635 opened on Oct 20, 2021

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

Repository metrics

Stars
 (5,381 stars)
PR merge metrics
 (No merged PRs in 30d)

Description

🐛 Bug

Usually the batch script with papermill runs automatically when triggered, but sometimes we need to press CTRL +C in order to continue the process or else it remains stuck. Usually CTRL+ C is use to terminate process, but sometime, I am facing this issue. Please let me know if there is a stable version which excludes this bug. Thanks

Contributor guide

Research direction
Investigate the batch script's interaction with papermill's execution, focusing on Ctrl+C signal handling. Check if there is a race condition or missing event handler causing the script to require manual interrupt to proceed.
Tech stack
python
Domain
databackend
Issue type
Bug
DifficultyEstimated implementation difficulty for a new contributor, from 1 for very small changes to 5 for expert-level work.
4
Estimated timeA rough time range for an experienced contributor to investigate, implement, test, and prepare a pull request.
1-2 days
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.
Unclear
Prerequisites
Pythonpapermill
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
30