Spurious warning emitted during fork() can deadlock a multi-threaded process
Open
Nobody has claimed this yet.
3.7 (EOL)
stdlib
type-bug
- Dominant language
- Python
- Stars
- 77.2k
- Forks
- 36k
- PR merge metrics
- PR metrics pending
Description
| BPO | 40442 |
|---|---|
| Nosy | @vstinner, @bowiechen, @rojer |
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-04-29.20:46:13.936>
labels = ['3.7', 'type-bug', 'library']
title = 'Spurious warning emitted during fork() can deadlock a multi-threaded process'
updated_at = <Date 2020-04-30.17:30:13.696>
user = 'https://github.com/rojer'
bugs.python.org fields:
activity = <Date 2020-04-30.17:30:13.696>
actor = 'bowiechen'
assignee = 'none'
closed = False
closed_date = None
closer = None
components = ['Library (Lib)']
creation = <Date 2020-04-29.20:46:13.936>
creator = 'rojer'
dependencies = []
files = []
hgrepos = []
issue_num = 40442
keywords = []
message_count = 1.0
messages = ['367701']
nosy_count = 4.0
nosy_names = ['vstinner', 'ionelmc', 'bowiechen', 'rojer']
pr_nums = []
priority = 'normal'
resolution = None
stage = None
status = 'open'
superseder = None
type = 'behavior'
url = 'https://bugs.python.org/issue40442'
versions = ['Python 3.7']
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 investigating the fork() behavior described in the issue, with attention to the interaction between the warning and a multi-threaded process. Determine which Library (Lib) code emits the warning and establish a reproduction before defining the expected behavior. Done means the spurious warning no longer permits the reported deadlock scenario.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- operating-systems
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100