Skip to content

Document asyncio behavior (logging and call to connection_lost) on socket TimeoutError #68765

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom
Closed
bitdancer opened this issue Jul 6, 2015 · 2 comments
Closed

Document asyncio behavior (logging and call to connection_lost) on socket TimeoutError #68765

bitdancer opened this issue Jul 6, 2015 · 2 comments
Labels
docs Documentation in the Doc dir topic-asyncio type-bug An unexpected behavior, bug, or error

Comments

@bitdancer
Copy link
Member

BPO 24577
Nosy @gvanrossum, @vstinner, @bitdancer, @1st1

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 2015-07-06.15:14:36.234>
labels = ['type-bug', 'docs', 'expert-asyncio']
title = 'Document asyncio behavior (logging and call to connection_lost) on socket TimeoutError'
updated_at = <Date 2015-07-06.15:36:36.216>
user = 'https://github.com/bitdancer'

bugs.python.org fields:

activity = <Date 2015-07-06.15:36:36.216>
actor = 'r.david.murray'
assignee = 'docs@python'
closed = False
closed_date = None
closer = None
components = ['Documentation', 'asyncio']
creation = <Date 2015-07-06.15:14:36.234>
creator = 'r.david.murray'
dependencies = []
files = []
hgrepos = []
issue_num = 24577
keywords = []
message_count = 1.0
messages = ['246370']
nosy_count = 5.0
nosy_names = ['gvanrossum', 'vstinner', 'r.david.murray', 'docs@python', 'yselivanov']
pr_nums = []
priority = 'normal'
resolution = None
stage = 'needs patch'
status = 'open'
superseder = None
type = 'behavior'
url = 'https://bugs.python.org/issue24577'
versions = ['Python 3.4', 'Python 3.5', 'Python 3.6']
@bitdancer
Copy link
Member Author

I saw _fatal_error tracebacks in my application log, and thought I had hit an asyncio bug, but according to python/asyncio#135 this is the correct behavior. That issue ends with a request to open a documentation issue on the python tracker, but I don't think that was done (I couldn't find one, anyway), so I'm opening this one.

At this point in time I have no idea where this would go in the docs. Maybe in the docs for connection_lost?

@bitdancer bitdancer added docs Documentation in the Doc dir topic-asyncio labels Jul 6, 2015
@bitdancer bitdancer added the type-bug An unexpected behavior, bug, or error label Jul 6, 2015
@bitdancer bitdancer changed the title Document behavior (logging and call to connection_lost) on socket TimeoutError Document asyncio behavior (logging and call to connection_lost) on socket TimeoutError Jul 6, 2015
@ezio-melotti ezio-melotti transferred this issue from another repository Apr 10, 2022
@ezio-melotti ezio-melotti moved this to Todo in asyncio Jul 17, 2022
@kumaraditya303
Copy link
Contributor

No activity for 7 years, no reproducer and things have changes a lot since then. If this is still a problem, create a new issue with reproducer for current supported versions.

@kumaraditya303 kumaraditya303 closed this as not planned Won't fix, can't repro, duplicate, stale Sep 11, 2022
Repository owner moved this from Todo to Done in asyncio Sep 11, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
docs Documentation in the Doc dir topic-asyncio type-bug An unexpected behavior, bug, or error
Projects
asyncio
Status: Done
Milestone
No milestone
Development

No branches or pull requests
2 participants
@bitdancer @kumaraditya303