Closed nilsnolde closed 4 years ago
I've started looking into it, and I could reproduce the error on different profiles as well. With profile=foot-walking
the error occurs 10-15% of the time, with driving-car
, driving-hgv
and cycling-regular
with about 0.5-1% of calls. However, I could not reproduce the error locally, neither with development nor with master branch code. I'm suspecting the issue might be related to server configuration or load situation or something. How do I find out if there are errors logged on the servers corresponding to the failing calls?
Same as #571 ?
Possible, now you mention it... As soon as the v6 code is deployed I'll run my repro code again to check, since #571 should be fixed now.
Did this get fixed?
I've run my repro code several times just to make sure, this got fixed when #571 got fixed.
Reported by a user. E.g. following query sometimes has an empty
extras
field: https://api.openrouteservice.org/directions?api_key=key&coordinates=11.976793,51.488623%7C13.40732,52.52045&profile=foot-walking&preference=shortest&language=de&format=json&geometry_format=geojson&elevation=true&maneuvers=true&extra_info=steepness%7Csuitability%7Csurface%7Cwaycategory%7Cwaytype%7Ctraildifficulty&instructions=trueTry 10-20 times, it will show up. The key exists, but no value, i.e.
extras: {}
in the response.It's a rather long route from Halle to Berlin. Sounds like a nasty thing to debug..