Occurs in the version 3.6 of aiohttp (present currently in focal).
When cancelling a connector task, the associated resolver task (if not finished) is not cancelled and continues running.
Unfortunately, if the resolver task eventually raises an exception (e.g., socket.gaierror), the exception will go directly to the exception handler because none will be awaiting the task anymore.
Occurs in the version 3.6 of aiohttp (present currently in focal).
When cancelling a connector task, the associated resolver task (if not finished) is not cancelled and continues running.
Unfortunately, if the resolver task eventually raises an exception (e.g., socket.gaierror), the exception will go directly to the exception handler because none will be awaiting the task anymore.
This is the root cause of https:/ /bugs.launchpad .net/ubuntu- power-systems/ +bug/1969393
The fix on aiohttp was backported to 3.7 but not to 3.6.
https:/ /github. com/aio- libs/aiohttp/ pull/5050