Bad proxy returned immediately after BaseManager server restarted
Open
Nobody has claimed this yet.
3.8 (EOL)
3.9 (EOL)
stdlib
topic-multiprocessing
- Dominant language
- Python
- Stars
- 77.2k
- Forks
- 36k
- PR merge metrics
- PR metrics pending
Description
| BPO | 42154 |
|---|
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-10-26.09:17:38.074>
labels = ['3.8', 'library', '3.9']
title = 'Bad proxy returned immediately after BaseManager server restarted'
updated_at = <Date 2020-10-26.09:17:38.074>
user = 'https://bugs.python.org/jryan'
bugs.python.org fields:
activity = <Date 2020-10-26.09:17:38.074>
actor = 'jryan'
assignee = 'none'
closed = False
closed_date = None
closer = None
components = ['Library (Lib)']
creation = <Date 2020-10-26.09:17:38.074>
creator = 'jryan'
dependencies = []
files = []
hgrepos = []
issue_num = 42154
keywords = []
message_count = 1.0
messages = ['379657']
nosy_count = 1.0
nosy_names = ['jryan']
pr_nums = []
priority = 'normal'
resolution = None
stage = None
status = 'open'
superseder = None
type = None
url = 'https://bugs.python.org/issue42154'
versions = ['Python 3.8', '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 with the original BPO issue 42154 and investigate BaseManager proxy behavior when its server restarts. Reproduce the immediate bad-proxy return, then identify the relevant multiprocessing library code and add coverage for the restart case; done means the proxy no longer returns immediately in that scenario.
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