Rapid
Rapid copied to clipboard
Handle OSM API Timeouts
Followup on #1304
We already handle a bunch of different error conditions with the OSM API.
But when things get really bad, we don't even get a response from the capabilities
or any of the other calls, just a connection timeout:
We should handle this situation too.