-
Notifications
You must be signed in to change notification settings - Fork 3.3k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Better handling of empty/corrupt data #693
Comments
springmeyer
pushed a commit
to Project-OSRM/node-osrm
that referenced
this issue
Aug 7, 2013
This is now implemented. Each of the file is checked for existence and file size 0. Errors will be caught like this: $ ./osrm-routed blank.ini
[warn] starting up engines, compiled at Aug 9 2013, 16:42:17
[info] loading graph data
[info] Data checksum is 1917857639
. 10% . 20% . 30% . 40% . 50% . 60% . 70% . 80% . 90% . 100% [info] Loading Timestamp
[info] Loading auxiliary information
[fatal error] exception: edges file is empty As usual, will be running tests now and push shortly afterwards. |
DennisOSRM
pushed a commit
that referenced
this issue
Aug 9, 2013
tested, this is working now, closing. Thanks! |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
I created a set of blank data like:
and a server.ini that pointed to them:
I am trying to simulate a failure writing these files and then a server process dynamically trying to read from them. On OS X via node-osrm this should throw at engine initialization but does not. I see suspiciously normal output like:
Then I can query the engine, which leads to a
SIGSEGV
:The text was updated successfully, but these errors were encountered: