Repository navigation
asyncio: If protocol_factory raises an error, the connection closes but no stacktrace is printed on the server. #70004
Description
| BPO | 25818 |
|---|---|
| Nosy | @gvanrossum, @vstinner, @1st1 |
| 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 = <Date 2015-12-07.22:45:09.965>
created_at = <Date 2015-12-07.22:33:02.586>
labels = ['invalid', 'expert-asyncio']
title = 'asyncio: If protocol_factory raises an error, the connection closes but no stacktrace is printed on the server.'
updated_at = <Date 2015-12-07.22:45:09.964>
user = 'https://bugs.python.org/SunDwarf'bugs.python.org fields:
activity = <Date 2015-12-07.22:45:09.964>
actor = 'abarry'
assignee = 'none'
closed = True
closed_date = <Date 2015-12-07.22:45:09.965>
closer = 'abarry'
components = ['asyncio']
creation = <Date 2015-12-07.22:33:02.586>
creator = 'SunDwarf'
dependencies = []
files = ['41265']
hgrepos = []
issue_num = 25818
keywords = []
message_count = 2.0
messages = ['256081', '256082']
nosy_count = 4.0
nosy_names = ['gvanrossum', 'vstinner', 'yselivanov', 'SunDwarf']
pr_nums = []
priority = 'normal'
resolution = 'not a bug'
stage = 'resolved'
status = 'closed'
superseder = None
type = None
url = 'https://bugs.python.org/issue25818'
versions = ['Python 3.4', 'Python 3.5']
Activity
SunDwarf commentedon Dec 7, 2015
This makes it a nightmare to figure out why your connections are abruptly closing. It should print an error at least.
[-]If protocol_factory raises an error, the connection closes but no stacktrace is printed on the server.[/-][+]asyncio: If protocol_factory raises an error, the connection closes but no stacktrace is printed on the server.[/+]SunDwarf commentedon Dec 7, 2015
I completely forgot asyncio has a debug mode. Ignore this.