concurrent.futures.ProcessPoolExecutor is unable to forward exceptions with state.
Open
Nobody has claimed this yet.
3.9 (EOL)
stdlib
topic-multiprocessing
type-bug
- Dominant language
- Python
- Stars
- 77.2k
- Forks
- 36k
- PR merge metrics
- PR metrics pending
Description
| BPO | 42769 |
|---|---|
| Files |
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 2020-12-28.16:37:04.784>
labels = ['type-bug', 'library', '3.9']
title = 'concurrent.futures.ProcessPoolExecutor is unable to forward exceptions with state.'
updated_at = <Date 2020-12-28.16:37:04.784>
user = 'https://bugs.python.org/damienlevac'
bugs.python.org fields:
activity = <Date 2020-12-28.16:37:04.784>
actor = 'damien.levac'
assignee = 'none'
closed = False
closed_date = None
closer = None
components = ['Library (Lib)']
creation = <Date 2020-12-28.16:37:04.784>
creator = 'damien.levac'
dependencies = []
files = ['49703']
hgrepos = []
issue_num = 42769
keywords = []
message_count = 1.0
messages = ['383903']
nosy_count = 1.0
nosy_names = ['damien.levac']
pr_nums = []
priority = 'normal'
resolution = None
stage = None
status = 'open'
superseder = None
type = 'behavior'
url = 'https://bugs.python.org/issue42769'
versions = ['Python 3.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.
Research direction
Start by running the linked repro.py to observe how ProcessPoolExecutor fails to forward exception state. Trace the ProcessPoolExecutor path responsible for propagating worker exceptions and identify the existing tests covering this behavior; done means the reproduction preserves the exception state when forwarded.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- backend, distributed-systems
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100