Control flow inconsistency on closed asyncio stream
Open
Nobody has claimed this yet.
OS-windows
topic-asyncio
type-bug
- Dominant language
- Python
- Stars
- 77.2k
- Forks
- 36k
- PR merge metrics
- PR metrics pending
Description
| BPO | 35840 |
|---|---|
| Nosy | @pfmoore, @tjguk, @asvetlov, @schlamar, @zware, @1st1, @zooba, @eamanu |
| 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-01-28.07:54:05.359>
labels = ['type-bug', '3.7', 'OS-windows', 'expert-asyncio']
title = 'Control flow inconsistency on closed asyncio stream'
updated_at = <Date 2019-02-25.18:57:20.343>
user = 'https://github.com/schlamar'
bugs.python.org fields:
activity = <Date 2019-02-25.18:57:20.343>
actor = 'eamanu'
assignee = 'none'
closed = False
closed_date = None
closer = None
components = ['Windows', 'asyncio']
creation = <Date 2019-01-28.07:54:05.359>
creator = 'schlamar'
dependencies = []
files = ['48082', '48160']
hgrepos = []
issue_num = 35840
keywords = []
message_count = 5.0
messages = ['334450', '334453', '336144', '336252', '336548']
nosy_count = 8.0
nosy_names = ['paul.moore', 'tim.golden', 'asvetlov', 'schlamar', 'zach.ware', 'yselivanov', 'steve.dower', 'eamanu']
pr_nums = []
priority = 'normal'
resolution = None
stage = None
status = 'open'
superseder = None
type = 'behavior'
url = 'https://bugs.python.org/issue35840'
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 comparing the two uploaded tcp_test.py reproductions (files 48082 and 48160) and examining the asyncio stream behavior when the stream is closed on Windows. Reproduce the inconsistent control flow and determine the expected behavior; done means the closed-stream path is consistent and covered by a regression test.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- networking
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100