tomhughes left a comment (openstreetmap/openstreetmap-website#7225)
Maybe I'm misunderstanding the problem, but this doesn't seem like the correct
solution to me...
As I understand it what happened is that the user activated the query tool, so
the router routed to `/query` but that page failed to load with a 503 error?
So the problem would seem to me to be that the router still calls the load
callback when the page has failed to load - it either shouldn't call it or
should provide an error indication so that it can show an error instead of
trying to start the overpass queries when it doesn't have the necessary HTML to
accept the results.
While this will fix the exception it's just a band aid rather than properly
fixing things surely?
--
Reply to this email directly or view it on GitHub:
https://github.com/openstreetmap/openstreetmap-website/pull/7225#issuecomment-4961095956
You are receiving this because you are subscribed to this thread.
Message ID:
<openstreetmap/openstreetmap-website/pull/7225/[email protected]>
_______________________________________________
rails-dev mailing list
[email protected]
https://lists.openstreetmap.org/listinfo/rails-dev