Repository navigation
Conversation
This branch has not been deployed
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
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.
Summary
Naive event datetimes were assigned the system's current UTC offset, which could shift the represented instant by one hour when the event date falls in a different daylight saving period. Use Python's local-time conversion for the specified date and preserve the existing rendering of aware values. For dates outside the platform conversion range, retain the existing current-offset fallback.
Verification


Confidence Score: 5/5
The PR appears safe to merge.Summary
Naive datetimes now use the local UTC offset for their event date, fixing errors across daylight saving periods.
No actionable issues found.
Reviews (1) · Last reviewed commit: "fix(serializer): resolve local timezone ..." · Reviewed by Greptile