ThreadPoolExecutor unbalanced semaphore count
Open
Nobody has claimed this yet.
3.11
stdlib
type-bug
- Dominant language
- Python
- Stars
- 77.2k
- Forks
- 36k
- PR merge metrics
- PR metrics pending
Description
| BPO | 44188 |
|---|---|
| Nosy | @pitrou, @asvetlov, @1st1, @Tinche, @bennieswart |
| PRs | |
| 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 2021-05-20.11:51:36.159>
labels = ['type-bug', 'library', '3.11']
title = 'ThreadPoolExecutor unbalanced semaphore count'
updated_at = <Date 2021-09-02.23:11:57.890>
user = 'https://github.com/bennieswart'
bugs.python.org fields:
activity = <Date 2021-09-02.23:11:57.890>
actor = 'tinchester'
assignee = 'none'
closed = False
closed_date = None
closer = None
components = ['Library (Lib)']
creation = <Date 2021-05-20.11:51:36.159>
creator = 'bennieswart'
dependencies = []
files = ['50054']
hgrepos = []
issue_num = 44188
keywords = ['patch']
message_count = 3.0
messages = ['394017', '400768', '400967']
nosy_count = 5.0
nosy_names = ['pitrou', 'asvetlov', 'yselivanov', 'tinchester', 'bennieswart']
pr_nums = ['26265']
priority = 'normal'
resolution = None
stage = 'patch review'
status = 'open'
superseder = None
type = 'behavior'
url = 'https://bugs.python.org/issue44188'
versions = ['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 by reading bug.py and the existing PR 26265 linked in the issue. Use the ThreadPoolExecutor unbalanced semaphore count described by the title as the behavior to investigate, and consider the work complete only when that count remains balanced.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- backend
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 20/100