[issue26278] BaseTransport.close() does not trigger connection_lost()

STINNER Victor added the comment: If a bug cannot be reproduced, it cannot be fixed. So I close the issue ;-) -- resolution: -> out of date stage: -> resolved status: open -> closed ___ Python tracker

[issue26278] BaseTransport.close() does not trigger connection_lost()

Sümer Cip added the comment: Closing the issue seems like a good idea: as it seems nobody seems to have spotted similar issue and I have only been able to reproduce it in Python 3.4. Just for future ref.: The uncommon thing is that the server I was using is a TCP game server holding

[issue26278] BaseTransport.close() does not trigger connection_lost()

Sümer Cip added the comment: I do not know I still have the issue since I have circumvented the problem. I have been using Python3.4, I think it was one of the earliest asyncio implementations. The way it can be reproduced is as following: 1) There are lots of active TCP connections

[issue26278] BaseTransport.close() does not trigger connection_lost()

anthony shaw added the comment: This issue was never responded to, are you still having this issue? Which version of CPython are you using and can you please provide steps to reproduce the problem. -- nosy: +anthonypjshaw ___ Python tracker

[issue26278] BaseTransport.close() does not trigger connection_lost()

New submission from Sümer Cip: Hi all, We have implemented a TCP server based on asyncio. And while doing some regression tests we randomly see following error: 1) Client connects to the server. 2) Client is closed ungracefully(without sending a FIN, deplug cable) 3) We have a custom PING