Message311728
| Author | asvetlov |
|---|---|
| Recipients | asvetlov, giampaolo.rodola, njs, yselivanov |
| Date | 2018-02-06.15:50:36 |
| SpamBayes Score | -1.0 |
| Marked as misclassified | Yes |
| Message-id | <1517932236.08.0.467229070634.issue32751@psf.upfronthosting.co.za> |
| In-reply-to |
| Content | |
|---|---|
Hmm, I don't see an easy way to fix it. awaiting for cancelled task potentially can wait forever. Adding another timeout looks too confusing. Iterating over a couple of loop steps is not reliable: try/finally block in awaited task can perform async IO with unpredictable completion time. |
|
| History | |||
|---|---|---|---|
| Date | User | Action | Args |
| 2018-02-06 15:50:36 | asvetlov | set | recipients: + asvetlov, giampaolo.rodola, njs, yselivanov |
| 2018-02-06 15:50:36 | asvetlov | set | messageid: <1517932236.08.0.467229070634.issue32751@psf.upfronthosting.co.za> |
| 2018-02-06 15:50:36 | asvetlov | link | issue32751 messages |
| 2018-02-06 15:50:36 | asvetlov | create | |