You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I get the output Server was started successfully and it even looks like the server starts at port 5000. However, I don't see all the output from docker in the jupyter notebook.
To get the server to really start successfully, I had to re-run the not just the code chunk above in the terminal, but I also had to do a full rebuild of the container in codespaces. After that rebuild, I had a successful server start in approx 2.5 minutes.
Hi @robcrystalornelas that is an interesting edge case. We integrated the three commands into the starting process such that these problems wouldn't occur. I'll look into it though. Thanks for bringing it up!
Claudio9701
changed the title
OSRM server issue
OSRM server issue: Handle subregions with more than continent-country level (e.g. south-america/brazil/sul)
Sep 5, 2023
Hi all 👋🏻 I've got an edge case I wanted to present w/ starting up the OSRM server in a GitHub codespace
If I accidentally (😭) run
up.routing.start_osrm_server('sul', 'south-america_brazil', 'foot');
without running the code below firstI get the output
Server was started successfully
and it even looks like the server starts at port 5000. However, I don't see all the output from docker in the jupyter notebook.To get the server to really start successfully, I had to re-run the not just the code chunk above in the terminal, but I also had to do a full rebuild of the container in codespaces. After that rebuild, I had a successful server start in approx 2.5 minutes.
CC: @bitsandbricks, @Claudio9701
The text was updated successfully, but these errors were encountered: