Skip to content

[3.13] gh-120683: Fix an error in logging.LogRecord timestamp (GH-120709) #120933

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 1 commit into from
Jun 24, 2024

Conversation

miss-islington
Copy link
Contributor

@miss-islington miss-islington commented Jun 24, 2024

The integer part of the timestamp can be rounded up, while the millisecond
calculation truncates, causing the log timestamp to be wrong by up to 999 ms
(affected roughly 1 in 8 million timestamps).
(cherry picked from commit 1500a23)

Co-authored-by: Serhiy Storchaka storchaka@gmail.com

…H-120709)

The integer part of the timestamp can be rounded up, while the millisecond
calculation truncates, causing the log timestamp to be wrong by up to 999 ms
(affected roughly 1 in 8 million timestamps).
(cherry picked from commit 1500a23)

Co-authored-by: Serhiy Storchaka <storchaka@gmail.com>
@miss-islington miss-islington requested a review from vsajip as a code owner June 24, 2024 06:50
@serhiy-storchaka serhiy-storchaka enabled auto-merge (squash) June 24, 2024 06:51
@serhiy-storchaka serhiy-storchaka merged commit 544a472 into python:3.13 Jun 24, 2024
35 checks passed
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.

2 participants