Tom Dryer

For anyone having issues with Google Voice contacts, #200 is a possible fix.

Sounds like something is blocking the IO loop. What operating system and hardware are you using? Is the CPU under high load when the issue occurs?

Network requests are asynchronous, so they shouldn't be blocking the IO loop. Try running hangups in asyncio debug mode: ``` PYTHONASYNCIODEBUG=1 hangups ``` While checking the logs for any messages...

Those logs indicate that that IO loop is blocked for 28 seconds. Is that the length of delay you've experienced? Is the hangups process idle during that time, or is...

Great! You can also specify `--notification-type none` to disable notifications. I'll re-purpose this issue for making the notification code asynchronous to prevent this from happening.

`No route to host` sounds like a networking problem. Can you try running this script? ```python import aiohttp import asyncio @asyncio.coroutine def main(): response = yield from aiohttp.request('GET', 'https://0.client-channel.google.com') print(response)...

What operating system are you using? I'd expect it to provide some kind of DNS cache.

You could try adding the relevant domain name to the hosts file to confirm whether DNS queries are the problem.

I think if you ignore the "observed" events, they'll pile up and the server will keep trying to send them. I noticed that hangups gets a lot of extra events...

Updated list based on Hangouts web: - [X] `adduser` - [X] `createconversation` - [ ] `declineallinvites` - [X] `deleteconversation` - [ ] `dismisssuggestedcontacts` - [X] `easteregg` - [X] `getconversation` -...