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.

Author gvanrossum
Recipients ajoino, alex.gronholm, asvetlov, chris.jerdonek, dreamsorcerer, gvanrossum, iritkatriel, jab, njs, tinchester, yselivanov
Date 2022-02-20.21:31:35
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1645392695.86.0.444421320132.issue46771@roundup.psfhosted.org>
In-reply-to
Content
(Sam Bull)
> To expand on this point, I've been looking at solving the race conditions in async-timeout. To see how such a race condition can end up with a task never exiting, take a look at this example: https://github.com/aio-libs/async-timeout/issues/229#issuecomment-908502523

This should be solved when using the cancel count -- the explicit cancel bumps the cancel count so the cancel scope (i.e. timeout()) will not raise TimeoutError.
History
Date User Action Args
2022-02-20 21:31:35gvanrossumsetrecipients: + gvanrossum, njs, jab, asvetlov, alex.gronholm, chris.jerdonek, yselivanov, tinchester, iritkatriel, dreamsorcerer, ajoino
2022-02-20 21:31:35gvanrossumsetmessageid: <1645392695.86.0.444421320132.issue46771@roundup.psfhosted.org>
2022-02-20 21:31:35gvanrossumlinkissue46771 messages
2022-02-20 21:31:35gvanrossumcreate