asyncio.Queue: putting items out of order when it is full
Open
Nobody has claimed this yet.
topic-asyncio
type-bug
- Dominant language
- Python
- Stars
- 77.2k
- Forks
- 36k
- PR merge metrics
- PR metrics pending
Description
| BPO | 38874 |
|---|---|
| Nosy | @asvetlov, @1st1, @MojoVampire, @rhdxmr |
| 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 2019-11-21.03:25:54.744>
labels = ['3.7', 'expert-asyncio']
title = 'asyncio.Queue: putting items out of order when it is full'
updated_at = <Date 2019-11-27.03:57:51.152>
user = 'https://github.com/rhdxmr'
bugs.python.org fields:
activity = <Date 2019-11-27.03:57:51.152>
actor = 'josh.r'
assignee = 'none'
closed = False
closed_date = None
closer = None
components = ['asyncio']
creation = <Date 2019-11-21.03:25:54.744>
creator = 'esrse'
dependencies = []
files = ['48740']
hgrepos = []
issue_num = 38874
keywords = []
message_count = 6.0
messages = ['357129', '357130', '357132', '357166', '357247', '357553']
nosy_count = 4.0
nosy_names = ['asvetlov', 'yselivanov', 'josh.r', 'esrse']
pr_nums = []
priority = 'normal'
resolution = None
stage = None
status = 'open'
superseder = None
type = None
url = 'https://bugs.python.org/issue38874'
versions = ['Python 3.7']
Linked PRs
- gh-112496
- gh-112501
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 running the uploaded poc-oooput.py reproducer and then read the asyncio.Queue implementation and its related tests. Confirm the observed ordering when the queue is full, and review linked PRs gh-112496 and gh-112501 before deciding whether any work remains.
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
- 25/100