-
Notifications
You must be signed in to change notification settings - Fork 20
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
Recording's file names have UTC date/time, not local #144
Comments
We'll add this to the changes coming with a new version that is in the works. It will take some time before they reach the V1Beta branch though, it is quite a change (code refactoring sounds cool in theory, but is pretty tough in practice). |
This is a kludged workaround. But since the stringifiedStartTime already has the timezone information stripped off, it has the end result of saving files with the expected time in the filename. P.S. I couldn't upload the patch as a .diff or .patch, so it's WorkoutRecorder.diff.txt |
Thanks. As said, we are doing major architecture changes at the moment where we will include a patch very similar to this. But as the recorders are an integral part of this change, we can't include it in the current V1Beta_updates as we don't want to risk frustrating integration of the new architecture later on. But it is on our radar. |
On a raspberry pi 3b+ with
The filenames created for the *_rowingData.csv, *_raw.csv and *_rowing.tcx files have the UTC date/time in them rather than the local time.
After 10 strokes:
I'm in Australia/Sydney time zone which is 10 hours ahead of UTC.
Assumption mode ON: I assume ORM isn't picking up the timezone, but I don't know how to fix this. The system timezone is correct.
The text was updated successfully, but these errors were encountered: