Skip to content
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

issue #313: handle out-of-order location notification #472

Merged
merged 1 commit into from
Jun 15, 2024

Conversation

patthoyts
Copy link
Contributor

This is a possible solution to issue #313

When receiving a location update check that it is newer than the last update from the same device before updating the 'last' record. This ensures the 'last' record is always the most recent update from the device in the event updates arrive out of order.

When receiving a location update check that it is newer than the last
update from the same device before updating the 'last' record. This
ensures the 'last' record is always the most recent update from the device
in the event updates arrive out of order.
@jpmens jpmens merged commit 61922fc into owntracks:master Jun 15, 2024
1 check passed
@jpmens
Copy link
Member

jpmens commented Jun 15, 2024

Thank you very much. Merged!

@patthoyts patthoyts deleted the pt/issue-313 branch June 15, 2024 11:32
jpmens added a commit that referenced this pull request Jul 23, 2024
- FIX: add card data to websocket notifications (#450)
- FIX: Enable building when WITH_TZ=no to disable timezone information (#473)
- FIX: view lastpos response (#471)
- FIX: handle out-of-order location notification in last/ (#472)
- FIX: drastically reduce memory leakage in views (#464)
- FIX: reformat json if it contains newlines/tabs before storing in .rec (#437)
- NEW: cached geo records can be auto-expired by setting OTR_CLEAN_AGE (#447)
- NEW: option -J prints variables in JSON format, for scripting
- NEW: version is printed in -J / -V
- FIX: in http mode friends' data must contain a topic; construct it or retrieve from last if available (#451)
- FIX: crash on non-string event name in _transition messages (#454)
- NEW: Add alt field to GeoJSON points parameters (#456)
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants