| FazBrowse GitHub Viewer | Trending | | Home |
| Tools: [Download Repo ZIP] [Original HTTPS Page] |
Sorry, something went wrong.
|
is there a test case we can add that would cover the issue and fix? |
Sorry, something went wrong.
There was a problem hiding this comment.
looks good, I do think closing the transport if the task is cancelled is the correct thing to do.
Sorry, something went wrong.
There was a problem hiding this comment.
thanks for adding a test case! LG!
Sorry, something went wrong.
|
Thanks @gvanrossum for the PR 🌮🎉.. I'm working now to backport this PR to: 3.11, 3.12. |
Sorry, something went wrong.
…task is cancelled (pythonGH-113690) (cherry picked from commit 4681a52) Co-authored-by: Guido van Rossum <guido@python.org>
…task is cancelled (pythonGH-113690) (cherry picked from commit 4681a52) Co-authored-by: Guido van Rossum <guido@python.org>
|
GH-113713 is a backport of this pull request to the 3.12 branch. |
Sorry, something went wrong.
|
GH-113714 is a backport of this pull request to the 3.11 branch. |
Sorry, something went wrong.
…task is cancelled (python#113690)
…task is cancelled (python#113690)
…task is cancelled (python#113690)
| Back | FazBrowse Home | New Git URL |
That callback exists purely to log an error when the coroutine running in the task raises an exception. But if the task was cancelled instead, the callback itself crashes, which just logs noise. In that case we should just close the transport without logging anything.
CC @jsundahl