-
Notifications
You must be signed in to change notification settings - Fork 125
fix: Return UTC-aware datetimes from unmarshalling #809
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
Open
abrookins
wants to merge
5
commits into
redis:main
Choose a base branch
from
abrookins:fix/datetime-timezone-aware
base: main
Could not load branches
Branch not found: {{ refName }}
Loading
Could not load tags
Nothing to show
Loading
Are you sure you want to change the base?
Some commits from the old base branch may be removed from the timeline,
and old review comments may become outdated.
Open
Changes from all commits
Commits
Show all changes
5 commits
Select commit
Hold shift + click to select a range
9411aa2
fix: Return UTC-aware datetimes from unmarshalling (#807)
abrookins 1d1e5e2
style: Format test file with ruff
abrookins 61fcb97
style: Format model.py with ruff
abrookins ac17c53
fix: Make test use UTC-aware datetime after fix
abrookins 1bff3fd
Merge branch 'main' into fix/datetime-timezone-aware
abrookins File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
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
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
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
Oops, something went wrong.
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.
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.
Date fields shift by one day in non-UTC timezones
High Severity
The retrieval path now uses
datetime.timezone.utcto interpret timestamps, butconvert_datetime_to_timestampstill storesdatetime.datevalues by combining with midnight in local time (naivedatetime.datetime.combine(obj, datetime.time.min).timestamp()). When the server is east of UTC, local midnight is the previous day in UTC, sofromtimestamp(value, utc).date()returns the wrong date. For example, a storeddate(2023, 1, 1)in UTC+5 round-trips asdate(2022, 12, 31).Additional Locations (1)
aredis_om/model/model.py#L116-L120