Fix Message.date timezone conversion causing logical errors in time comparison #193
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.
The
timestamp_to_datetime()
function inpyrogram/utils.py
was incorrectly converting Unix timestamps to datetime objects, causingMessage.date
to have wrong timezone information. This led to logical errors when users compared message timestamps with current time.Problem
The issue occurred when users in non-UTC timezones performed time comparisons:
For users in Europe/Kiev timezone (UTC+3), a message timestamp that should represent "22:00:12 UTC" was incorrectly converted to "01:00:12 UTC", making messages appear 3 hours newer than they actually were.
Root Cause
The
timestamp_to_datetime()
function used:This approach:
.replace()
Solution
Changed to the correct implementation:
This properly interprets Unix timestamps as UTC time, ensuring consistent datetime objects regardless of the user's system timezone.
Validation
Fixes #192.
💡 You can make Copilot smarter by setting up custom instructions, customizing its development environment and configuring Model Context Protocol (MCP) servers. Learn more Copilot coding agent tips in the docs.