Message344552
> 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? |
|
Date |
User |
Action |
Args |
2019-06-04 12:08:53 | vstinner | set | recipients:
+ vstinner, asvetlov, lukasz.langa, yselivanov |
2019-06-04 12:08:53 | vstinner | set | messageid: <1559650133.81.0.631887203366.issue34037@roundup.psfhosted.org> |
2019-06-04 12:08:53 | vstinner | link | issue34037 messages |
2019-06-04 12:08:53 | vstinner | create | |
|