Changing pollers to use UTC time #109
Merged
Conversation
This file contains 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
mtlynch
added a commit
to mtlynch/GreenPiThumb_Frontend
that referenced
this pull request
Apr 2, 2017
RecordEncoder doesn't actually do anything record-specific and we have other objects (image metadata) that we want to encode with JSON. A normal JSON encoder can't encode datetimes, but we can just make RecordEncoder a generic Encoder that encodes datetimes as ISO-8601. Also makes the small change that timestamps are assumed to be in UTC time zone, related to the changes in the backend: * JeetShetty/GreenPiThumb#101 * JeetShetty/GreenPiThumb#109 Changes the serialized format to append a Z (representing UTC time zone) instead of an offset from UTC in hours.
mtlynch
added a commit
to mtlynch/GreenPiThumb_Frontend
that referenced
this pull request
Apr 2, 2017
RecordEncoder doesn't actually do anything record-specific and we have other objects (image metadata) that we want to encode with JSON. A normal JSON encoder can't encode datetimes, but we can just make RecordEncoder a generic Encoder that encodes datetimes as ISO-8601. Also makes the small change that timestamps are assumed to be in UTC time zone, related to the changes in the backend: * JeetShetty/GreenPiThumb#101 * JeetShetty/GreenPiThumb#109 Changes the serialized format to append a Z (representing UTC time zone) instead of an offset from UTC in hours.
JeetShetty
approved these changes
Apr 3, 2017
mtlynch
added a commit
to mtlynch/GreenPiThumb_Frontend
that referenced
this pull request
Apr 3, 2017
RecordEncoder doesn't actually do anything record-specific and we have other objects (image metadata) that we want to encode with JSON. A normal JSON encoder can't encode datetimes, but we can just make RecordEncoder a generic Encoder that encodes datetimes as ISO-8601. Also makes the small change that timestamps are assumed to be in UTC time zone, related to the changes in the backend: * JeetShetty/GreenPiThumb#101 * JeetShetty/GreenPiThumb#109 Changes the serialized format to append a Z (representing UTC time zone) instead of an offset from UTC in hours.
mtlynch
added a commit
to JeetShetty/GreenPiThumb_Frontend
that referenced
this pull request
Apr 5, 2017
RecordEncoder doesn't actually do anything record-specific and we have other objects (image metadata) that we want to encode with JSON. A normal JSON encoder can't encode datetimes, but we can just make RecordEncoder a generic Encoder that encodes datetimes as ISO-8601. Also makes the small change that timestamps are assumed to be in UTC time zone, related to the changes in the backend: * JeetShetty/GreenPiThumb#101 * JeetShetty/GreenPiThumb#109 Changes the serialized format to append a Z (representing UTC time zone) instead of an offset from UTC in hours.
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.
No description provided.