Repository navigation
Conversation
Naive XCom datetimes represent wall-clock values rather than instants, so serializing them as local timestamps changes their value when workers use different timezones. Preserve the wall-clock representation while retaining compatibility with existing payloads. Co-authored-by: Copilot <[email protected]>
|
Hello @Kunal8954 - thank you for your contributions to Apache Airflow! The Airflow community has introduced a limit of 5 open pull requests at a time for contributors without write access to the repository. You currently have 8 open pull requests, so - as a one-time step of introducing the limit - we closed the ones where maintainers have not engaged yet:
These pull requests stay open because maintainers are already engaged in them - they count towards your limit:
This is not a judgement of you or of your changes. We never told contributors before that opening many pull requests at once was a problem, so there is nothing to feel bad about - and nothing is lost: your branches, commits and the review history stay where they are. What we ask you to do is to make your first prioritization decision: choose which of the pull requests above matter most to you, and reopen them (up to 5 open at a time, including the ones still open) with the "Reopen pull request" button or While your pull requests are waiting for review, the most valuable thing you can do is help in other ways - reviewing other contributors' pull requests, helping with issues, and taking part in the discussions on the devlist and Slack. Why we introduced the limit, what it means for you and how to reopen or restore a pull request is explained in https://github.com/apache/airflow/blob/main/contributing-docs/32_open_pull_request_limit.rst. Drafted-by: Claude Code (Opus 5); reviewed by @potiuk before posting |
Naive
datetimevalues are wall-clock values, but the current XCom serializer converts them through local timestamps. When workers use different OS timezones, deserialization changes the value.This keeps aware datetime serialization backward compatible, serializes naive datetimes as ISO wall-clock strings, and retains readability for existing version-2 payloads. Regression coverage verifies the new representation and legacy compatibility.
closes: #72635
Was generative AI tooling used to co-author this PR?
Generated-by: Copilot (GPT-5) following the guidelines