Try to fix time difference issues of timeseries2csv #19
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
stephanritscher
force-pushed
the
main
branch
from
8abdf8f to
8baa4f6
Compare
stephanritscher
force-pushed
the
main
branch
from
1fc6e38 to
7720dae
Compare
stephanritscher
force-pushed
the
main
branch
from
dd514b8 to
eb394cb
Compare
stephanritscher
force-pushed
the
main
branch
from
eb394cb to
723901d
Compare
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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.
As I argued in #7, I think RCT power devices handle timezone information incorrectly when converting between readable dates and timestamps. This PR tries to address this problem.