Skip to content

fix: use timezone-aware S3 partition timestamps - #788

Closed
Ghraven wants to merge 1 commit into
apache:mainfrom
Ghraven:fix/s3client-timezone-aware-partitions
Closed

Ghraven wants to merge 1 commit into
apache:mainfrom
Ghraven:fix/s3client-timezone-aware-partitions

Conversation

@Ghraven

@Ghraven Ghraven commented May 24, 2026

Copy link
Copy Markdown
Contributor

Summary

  • replace deprecated datetime.utcnow() in the S3 tracking client partition timestamp
  • use datetime.now(datetime.timezone.utc) so generated partition timestamps are timezone-aware

Before / after

Before, S3TrackingClient.save() generated a naive UTC timestamp with datetime.datetime.utcnow().isoformat().
After, it generates an explicit UTC timestamp such as 2026-05-24T03:12:34+00:00.

Verification

  • python -m py_compile burr/tracking/s3client.py
  • git diff --check

@github-actions github-actions Bot added the area/tracking Telemetry, tracing, OpenTelemetry label May 24, 2026
@github-actions

Copy link
Copy Markdown

This PR has had no activity for 96 days.
Closing to keep the PR list manageable.

Feel free to reopen when you are ready to continue.
If the branch has conflicts, a fresh PR against main might be easier.

@github-actions github-actions Bot closed this Aug 31, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

area/tracking Telemetry, tracing, OpenTelemetry

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant