消息 [344552] - Python tracker

➜

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.

作者	vstinner
收信人	asvetlov, lukasz.langa, vstinner, yselivanov
日期	2019-06-04.12:08:53
SpamBayes Score	-1.0
Marked as misclassified	是
Message-id	<1559650133.81.0.631887203366.issue34037@roundup.psfhosted.org>
In-reply-to

内容
> The problem is that loop.close() can "hang" for minutes if there are pending background jobs or slow DNS resolution requests. Maybe concurrent.futures should be enhanced for that? Or from asyncio, is it possible to poll the executor and emit a warning if some threads take longer than <threshold in esconds>? It would be great if we could display repr() of the slow job in that case. Yury also asked for a timeout, but it's not supported by concurrent.futures yet, and I'm not sure what should be done in case of timeout? Retry? Log a warning?

> The problem is that loop.close() can "hang" for minutes if there are pending background jobs or slow DNS resolution requests.

Maybe concurrent.futures should be enhanced for that?

Or from asyncio, is it possible to poll the executor and emit a warning if some threads take longer than <threshold in esconds>? It would be great if we could display repr() of the slow job in that case.

Yury also asked for a timeout, but it's not supported by concurrent.futures yet, and I'm not sure what should be done in case of timeout? Retry? Log a warning?

历史
日期	用户	动作	参数
2019-06-04 12:08:53	vstinner	修改	recipients: + vstinner, asvetlov, lukasz.langa, yselivanov
2019-06-04 12:08:53	vstinner	修改	messageid: <1559650133.81.0.631887203366.issue34037@roundup.psfhosted.org>
2019-06-04 12:08:53	vstinner	链接	issue34037 messages
2019-06-04 12:08:53	vstinner	创建