multiprocessing breaks when payload fails to unpickle
Open
Nobody has claimed this yet.
3.8 (EOL)
stdlib
topic-multiprocessing
type-bug
- Dominant language
- Python
- Stars
- 77.2k
- Forks
- 36k
- PR merge metrics
- PR metrics pending
Description
| BPO | 39751 |
|---|---|
| Nosy | @warsaw, @bitdancer, @iritkatriel |
| 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-02-25.16:37:00.081>
labels = ['type-bug', '3.8', 'expert-email']
title = 'multiprocessing breaks when payload fails to unpickle'
updated_at = <Date 2021-09-07.19:38:22.546>
user = 'https://bugs.python.org/JooEiras'
bugs.python.org fields:
activity = <Date 2021-09-07.19:38:22.546>
actor = 'iritkatriel'
assignee = 'none'
closed = False
closed_date = None
closer = None
components = ['email']
creation = <Date 2020-02-25.16:37:00.081>
creator = 'Jo\xc3\xa3o Eiras'
dependencies = []
files = ['48915']
hgrepos = []
issue_num = 39751
keywords = []
message_count = 2.0
messages = ['362649', '401339']
nosy_count = 4.0
nosy_names = ['barry', 'r.david.murray', 'Jo\xc3\xa3o Eiras', 'iritkatriel']
pr_nums = []
priority = 'normal'
resolution = None
stage = None
status = 'open'
superseder = None
type = 'behavior'
url = 'https://bugs.python.org/issue39751'
versions = ['Python 3.8']
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 reading the uploaded test case, test_multiproc_error_unpickle.py, and trace the multiprocessing path exercised when the payload cannot be unpickled. Confirm the current failure behavior and define done as handling that failure without breaking multiprocessing; add or adapt regression coverage around the test case.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- distributed-systems
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100