fix: use aware UTC for S3 log partitions#811
Merged
Merged
Conversation
elijahbenizzy
approved these changes
Jun 20, 2026
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
2 participants
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.
Problem: S3TrackingClient._get_time_partition() used datetime.datetime.utcnow(), which is deprecated and returns a naive UTC timestamp.
Before / after: before, S3 log partition keys were derived from a naive UTC timestamp. After, they are derived from datetime.datetime.now(datetime.UTC), preserving UTC partitioning while avoiding the deprecated API.
Verification: python -m py_compile burr\tracking\s3client.py