Raising an exception that cannot be unpickled causes hang in ProcessPoolExecutor
Nobody has claimed this yet.
Assessment
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Newbie friendliness
- 25/100
- Issue type
- Bug
- Clarity
- Needs clarification
- Activity status
- Stale
- Tech stack
- python
- Domain
- distributed-systems
Research direction
Start at the ProcessPoolExecutor entry point and reproduce the hang with an exception that cannot be unpickled. Trace the worker and result-handling paths, then identify the existing tests for ProcessPoolExecutor; done means the failure no longer hangs and the relevant test coverage passes.
Written by the indexing model from the issue text.
Description
| BPO | 24900 |
|---|---|
| Nosy | @pitrou, @avassalotti, @agronholm, @serhiy-storchaka |
Note: these values reflect the state of the issue at the time it was migrated and might not reflect the current state.
Show more details
GitHub fields:
assignee = None
closed_at = None
created_at = <Date 2015-08-20.07:21:49.990>
labels = []
title = 'Raising an exception that cannot be unpickled causes hang in ProcessPoolExecutor'
updated_at = <Date 2017-08-30.23:21:01.986>
user = 'https://bugs.python.org/filmor'
bugs.python.org fields:
activity = <Date 2017-08-30.23:21:01.986>
actor = 'pitrou'
assignee = 'none'
closed = False
closed_date = None
closer = None
components = []
creation = <Date 2015-08-20.07:21:49.990>
creator = 'filmor'
dependencies = []
files = []
hgrepos = []
issue_num = 24900
keywords = []
message_count = 4.0
messages = ['248878', '248879', '249531', '250385']
nosy_count = 5.0
nosy_names = ['pitrou', 'alexandre.vassalotti', 'filmor', 'alex.gronholm', 'serhiy.storchaka']
pr_nums = []
priority = 'normal'
resolution = None
stage = None
status = 'open'
superseder = None
type = None
url = 'https://bugs.python.org/issue24900'
versions = ['Python 2.7', 'Python 3.2', 'Python 3.3', 'Python 3.4', 'Python 3.5', 'Python 3.6']
- Dominant language
- Python
- Stars
- 77.2k
- Forks
- 36k
- Avg merge
- 1d 9h
- Merged PRs (30d)
- 558
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 python/cpython
-
docs pending
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
-
stdlib type-feature
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
-
stdlib type-feature
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
-
build type-bug
Difficulty 2/5 1-3 hours Newbie friendliness 76/100
-
stdlib topic-email type-feature
Difficulty 2/5 1-3 hours Newbie friendliness 70/100
Similar issues
-
area/auth bug comp/agent P3 platform/discord type/security
Difficulty 2/5 1-3 hours Newbie friendliness 88/100
NousResearch/hermes-agent#117848 ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 74/100
bancolombia/sentinel#23 ·
-
test md OpenCI
Difficulty 2/5 1-3 hours Newbie friendliness 74/100
-
integration:quickjs org:external priority:backlog topic:code-interpreter topic:middleware type:feature
Difficulty 2/5 1-3 hours Newbie friendliness 74/100
langchain-ai/deepagents#6450 ·
-
bug client
Difficulty 2/5 1-3 hours Newbie friendliness 88/100