-
Notifications
You must be signed in to change notification settings - Fork 0
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
Measures fail (probably timezone related) #92
Milestone
Comments
If I add 1 day server time at 1/2 for measure 85105
Then, the computation seams correct. |
MathieuNls
added a commit
that referenced
this issue
Jan 5, 2016
MathieuNls
added a commit
that referenced
this issue
Jan 5, 2016
Closed
Si jamais t'as une dispo demain, je veux bien qu'on se capte pour un Skype en vitesse ! |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
The user claims to be on Pacific timezone (UTC -9) and most of his measure are at UTC-9, so this information holds.
However, when the user make a measure after 3 p.m pacific time (00:00 am the next day UTC time), the day is not incremented on the MRT and ART fields (MeasureReferenceTime and AccuracyReferenceTime) which represent the server time for measure 1/2 and 2/2, respectively.
See measures with diffs around -15 hours in the following extract.
The text was updated successfully, but these errors were encountered: