This issue tracker has been migrated to GitHub, and is currently read-only.
For more information, see the GitHub FAQs in the Python's Developer Guide.

Title: asyncio IocpProactor bug
Type: Stage: resolved
Components: asyncio Versions: Python 3.7
Status: closed Resolution: duplicate
Dependencies: Superseder: False timeout log message on proactor close
View: 34323
Assigned To: Nosy List: asvetlov,, vstinner, yselivanov
Priority: normal Keywords:

Created on 2018-12-28 01:22 by, last changed 2022-04-11 14:59 by admin. This issue is now closed.

Messages (3)
msg332632 - (view) Author: Jeff Robbins ( * Date: 2018-12-28 01:22
The close() method of IocpProactor in has this code in its close() method:

        while self._cache:
            if not self._poll(1):
                logger.debug('taking long time to close proactor')

The bug is that self._poll() has *no* return statements in it, and so returns None no matter what.  Which makes the "if not" part confusing, at best.  At worst, it might reflect a disconnect with the author's intent.

I added a bit more logging and re-ran my test:

        while self._cache:
            logger.debug('before self._poll(1)')
            if not self._poll(1):
                logger.debug('taking long time to close proactor')

logger output:

20:16:30.247 (D)   MainThread                      asyncio: before self._poll(1)
20:16:30.248 (D)   MainThread                      asyncio: taking long time to close proactor
20:16:30.249 (D)   MainThread                      asyncio: {}

Obviously 1 millisecond isn't "taking a long time to close proactor".  Also of interest, the _cache is now empty.  

I think the intent of the author must have been to check if the call to ._poll() cleared out any possible pending futures, or waited the full 1 second.  Since ._poll() doesn't return any value to differentiate if it waited the full wait period or not, the "if" is wrong, and, I think, the intent of the author isn't met by this code.

But, separate from speculating on "intent", the debug output of "taking a long time to close proactor" seems wrong, and the .close() code seems disassociated with the implementation of ._poll() in the same class IocpProactor in
msg332735 - (view) Author: Jeff Robbins ( * Date: 2018-12-29 21:04
This issue is likely a duplicate of
which was reported in Python 3.5.
msg333690 - (view) Author: STINNER Victor (vstinner) * (Python committer) Date: 2019-01-15 12:09
I confirm that it's a duplicate of bpo-34323 that I just fixed ;-)
Date User Action Args
2022-04-11 14:59:09adminsetgithub: 79780
2019-01-15 12:09:20vstinnersetstatus: open -> closed

superseder: False timeout log message on proactor close

nosy: + vstinner
messages: + msg333690
resolution: duplicate
stage: resolved
2018-12-29 21:04:55jeffr@livedata.comsetmessages: + msg332735
2018-12-28 01:22:04jeffr@livedata.comcreate