Fix: resolving bug where timeseries x-axis is ahead by one hour #92
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
arvinpoddar
requested review from
salcock,
akram-rameez,
albertodainotti and
amandahmeng
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.
Aniket discovered that times between daylight savings in prod are currently one hour ahead of the actual UTC time (when visualized on the chart). After investigation, the issue is likely due to converting a UTC time to ET, then back to UTC.
This fix uses the raw UTC timestamp from the API instead of performing any intermediate conversions. This fix was validated against GTR data and members of OONI (for international correctness).