-
Notifications
You must be signed in to change notification settings - Fork 41
Fixes #846 #847
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
Fixes #846 #847
Conversation
Signed-off-by: Alexis <[email protected]>
1eb4106
to
793b720
Compare
Would you be able to confirm that the timestamp client here properly handles timezones/UTC? I would assume yes since we're just using the standard library. |
Codecov ReportAll modified and coverable lines are covered by tests ✅
Additional details and impacted files@@ Coverage Diff @@
## main #847 +/- ##
==========================================
- Coverage 52.85% 45.92% -6.94%
==========================================
Files 20 55 +35
Lines 1209 2942 +1733
==========================================
+ Hits 639 1351 +712
- Misses 509 1451 +942
- Partials 61 140 +79 ☔ View full report in Codecov by Sentry. |
Yes - confirmed this this morning. |
Signed-off-by: Alexis <[email protected]>
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
final approval will defer to @haydentherapper
Thank you! |
Summary
This PR fixes the problem highlighted in #846 .
Release Note
FIX TimestampResponse Time were not properly returned as GMT.
Documentation
None