[issue33833] ProactorEventLoop raises AssertionError

STINNER Victor added the comment: Why not fixing Python 3.6? It is not affected? -- ___ Python tracker ___ ___ Python-bugs-list mai

[issue33833] ProactorEventLoop raises AssertionError

Change by Andrew Svetlov : -- resolution: -> fixed stage: patch review -> resolved status: open -> closed ___ Python tracker ___ __

[issue33833] ProactorEventLoop raises AssertionError

miss-islington added the comment: New changeset d5c75be55504fae1ff510eed66cddbd27bfbdbe2 by Miss Islington (bot) in branch '3.7': bpo-33833: Fix ProactorSocketTransport AssertionError (GH-7893) https://github.com/python/cpython/commit/d5c75be55504fae1ff510eed66cddbd27bfbdbe2 -- nosy

[issue33833] ProactorEventLoop raises AssertionError

Change by miss-islington : -- pull_requests: +8082 ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe: https://ma

[issue33833] ProactorEventLoop raises AssertionError

Andrew Svetlov added the comment: New changeset 9045199c5aaeac9b52537581be127d999b5944ee by Andrew Svetlov (twisteroid ambassador) in branch 'master': bpo-33833: Fix ProactorSocketTransport AssertionError (#7893) https://github.com/python/cpython/commit/9045199c5aaeac9b52537581be127d999b5944e

[issue33833] ProactorEventLoop raises AssertionError

twisteroid ambassador added the comment: As an aside, I'm wondering whether it makes sense to add a blanket "assert exception handler has not been called" condition to ProactorEventLoop's tests, or even other asyncio tests. It looks like ProactorEventLoop is more prone to dropping exceptions

[issue33833] ProactorEventLoop raises AssertionError

twisteroid ambassador added the comment: No problem. Running the attached test script on latest master, Windows 10 1803, several errors like this are logged: Exception in callback _ProactorBaseWritePipeTransport._loop_writing(<_OverlappedF...events.py:479>) handle: ) created at %USERPROFIL

[issue33833] ProactorEventLoop raises AssertionError

STINNER Victor added the comment: > Sometimes when a socket transport under ProactorEventLoop is writing while > the peer closes the connection, asyncio logs an AssertionError. Would you mind to add an example of such error in this issue? -- ___

[issue33833] ProactorEventLoop raises AssertionError

Change by twisteroid ambassador : -- pull_requests: +7500 ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe: htt

[issue33833] ProactorEventLoop raises AssertionError

Yury Selivanov added the comment: Adding Victor as he's been helping with asyncio/proactor lately. -- nosy: +vstinner ___ Python tracker ___ __

[issue33833] ProactorEventLoop raises AssertionError

Change by twisteroid ambassador : -- keywords: +patch pull_requests: +7251 stage: -> patch review ___ Python tracker ___ ___ Python

[issue33833] ProactorEventLoop raises AssertionError

Change by twisteroid ambassador : -- type: -> behavior ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe: https

[issue33833] ProactorEventLoop raises AssertionError

New submission from twisteroid ambassador : Sometimes when a socket transport under ProactorEventLoop is writing while the peer closes the connection, asyncio logs an AssertionError. Attached is a script that fairly reliably reproduces the behavior on my computer. This is caused by _Proacto