Bug fix to load_timeline_for_day_and_user #1061
Open
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
…nd phone data timestamps - Added functionality to find and store the most recent location and phone data timestamps during the loading process. - Updated user profile with the latest timestamps after loading entries. - Initialized pipeline range if not already set to ensure proper processing of data.
JGreenlee
approved these changes
May 13, 2025
shankari
force-pushed
the
master
branch
4 times, most recently
from
a2a9a44 to
e50e9f3
Compare
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Addresses the issue where data wasn't being processed by the pipeline due to date being set to 1970.
This update tracks most recent location timestamp from background/location. Also tracks latest phone data timestamp from metadata.
Some real examples result in key error in case of things, I added checks for fields to prevent these key errors
After loading the data, we now update the user profile with these timestamps to reflect the newly loaded data. It also initializes the pipeline_range field if doesn't exist.
These fixes should ensure that profiles are properly updated with timestamps so it won't be skipped.