-
Notifications
You must be signed in to change notification settings - Fork 31
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
Compass broke after trip #42
Comments
So here's the entry that caused the issue:
I changed the code so it could process these: if (array_key_exists('geometry', $loc)) {
if($loc['geometry']['coordinates'][0] == 0 && $loc['geometry']['coordinates'][1] == 0) $shouldAdd = false;
} else {
\Log::debug("something went wrong, no geometry, skipping, but srsly, wtf");
\Log::debug(print_r($loc, true));
} I think what happened is that I am in the middle of switching phones and at one point both were logging and that does not jibe well with Compass somehow. |
That's super weird, it shouldn't be possible for Overland to generate a record that doesn't have location data! The other way to avoid this is to turn off the "tracking stats" feature in the app. but yeah if you're pushing data from two phones you'll also run into the problem of the records being out of order since it currently assumes data is always written sequentially. |
Yeah, I really don't know what happened, and as far as I can tell it was this one record. Since than I reset the other phone so now I have definitely only one copy of overland running. Still, might be wise to add something like the above to the code for these freak incidents. |
I was on a trip to another country. I'm back now and it suddenly throws 500 errors with overland. I had it running on the airplane, maybe that messed things up somehow?
The text was updated successfully, but these errors were encountered: