Multiprocessing Manager Client Not Reconnecting
Open
Nobody has claimed this yet.
3.10
3.11
3.9 (EOL)
stdlib
topic-multiprocessing
type-bug
- Dominant language
- Python
- Stars
- 77.2k
- Forks
- 36k
- PR merge metrics
- PR metrics pending
Description
| BPO | 43329 |
|---|---|
| Nosy | @pitrou, @ethanfurman, @serhiy-storchaka, @applio |
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 2021-02-26.14:31:42.237>
labels = ['type-bug', 'library', '3.9', '3.10', '3.11']
title = 'Multiprocessing Manager Client Not Reconnecting'
updated_at = <Date 2021-10-03.00:43:35.717>
user = 'https://bugs.python.org/boom0192'
bugs.python.org fields:
activity = <Date 2021-10-03.00:43:35.717>
actor = 'boom0192'
assignee = 'none'
closed = False
closed_date = None
closer = None
components = ['Library (Lib)']
creation = <Date 2021-02-26.14:31:42.237>
creator = 'boom0192'
dependencies = []
files = []
hgrepos = []
issue_num = 43329
keywords = []
message_count = 5.0
messages = ['387726', '396093', '396094', '396115', '403068']
nosy_count = 5.0
nosy_names = ['pitrou', 'ethan.furman', 'serhiy.storchaka', 'davin', 'boom0192']
pr_nums = []
priority = 'normal'
resolution = None
stage = None
status = 'open'
superseder = None
type = 'behavior'
url = 'https://bugs.python.org/issue43329'
versions = ['Python 3.9', 'Python 3.10', 'Python 3.11']
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 with the linked BPO issue 43329 and its five-message discussion to recover the reproduction and expected behavior. The payload names no source file, entry point, or test, so trace the multiprocessing Manager client behavior from there. Done means the reported client reconnection failure is reproducible, corrected, and covered by appropriate regression validation.
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
- 25/100