Joongi Kim

I've faced similar problems when I play with coroutines. As @housleyjk noted out, usually letting the main event loop to progress once more makes the things to clean up properly....

I think you could wrap it using [`asyncio.wait_for()`](https://docs.python.org/3/library/asyncio-task.html#asyncio.wait_for) with timeout parameter.

I believe that the exception handler for an asyncio event loop should be a normal function, not a coroutine function. The documentation says it's just a callable.

Tried running your snippet, and I got many strange behaviors, such as haning or infinite loop of exception handlers, etc., even after changing the exception handler to just print messages...

If you want to keep using `aiologger`, I'd suggest to use [`janus`](https://github.com/aio-libs/janus) to mediate the synchronous loop exception handler and a separate logger coroutine task. Maybe you might be interested...

Since Python 3.8, `asyncio.CancelledError` became a `BaseException` (not `Exception`), your example works as expected in Python 3.8 (raising cancellation error after 1 second). Though, we need to add a separate...

I just ran into the same issue on Ruby 2.1 x64 + Windows 8.1, and found another solution: https://stackoverflow.com/questions/5720484/how-to-solve-certificate-verify-failed-on-windows/16134586#16134586 .

Yes. When I get some free time, I will make a PR for this.

Okay, I found that authentication failure happens with new EC2 instances from a **custom AMI** (created before masterkey renewal) only. This means that the key renewal process has gone flawlessly...

After some experiments, I found that giving cloud-config to change default username (specific to my environment) in the instance launch wizard fixes the authentication problem. It will be nice if...