Skip to content

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

Merged
merged 2 commits into from
Oct 7, 2024
Merged

Fixes #846 #847

merged 2 commits into from
Oct 7, 2024

Conversation

DarkaMaul
Copy link
Contributor

Summary

This PR fixes the problem highlighted in #846 .

Release Note

FIX TimestampResponse Time were not properly returned as GMT.

Documentation

None

@DarkaMaul DarkaMaul requested a review from a team as a code owner October 4, 2024 16:13
Signed-off-by: Alexis <[email protected]>
@haydentherapper
Copy link
Contributor

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.

haydentherapper
haydentherapper previously approved these changes Oct 4, 2024
Copy link

codecov bot commented Oct 4, 2024

Codecov Report

All modified and coverable lines are covered by tests ✅

Project coverage is 45.92%. Comparing base (6fd19b0) to head (157a5ac).
Report is 194 commits behind head on main.

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.
📢 Have feedback on the report? Share it here.

@DarkaMaul
Copy link
Contributor Author

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.

Yes - confirmed this this morning.

Signed-off-by: Alexis <[email protected]>
Copy link
Member

@cpanato cpanato left a 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

@haydentherapper
Copy link
Contributor

Thank you!

@haydentherapper haydentherapper merged commit 55a31ad into sigstore:main Oct 7, 2024
8 checks passed
@DarkaMaul DarkaMaul deleted the dm/fix-time-utc branch October 7, 2024 14:47
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants