Closed Mariusthvdb closed 9 months ago
Thanks. I got that when I first used geopy. I increased the default timeout of 1 sec to 3 sec and it went away. Looks like I need to make it bigger. If you want to try and see what works for you, change NOM_TIMEOUT in const.py.
I'll also add something to catch that exception in case it still happens in the future.
Should be fixed in 1.0.0b8.
Please see below. Also noticed a startup timeout, and a spontaneous restart. I am not 100% certain entity-tz caused this, but it occurred after having installed the new beta, and the instance got unresponsive during its first restart. Dont see those spontaneous restarts often, hardly ever tbh, so I link to to this for now. Might be caused by the same timeout error?
as a result of which all entities, so not only the new country and address entities go 'unknown':