Repository navigation
Fix serialization of datetimes with a fixed UTC offset - #74922
Open
justinpakzad wants to merge 1 commit into
Open
justinpakzad wants to merge 1 commit into
justinpakzad wants to merge 1 commit into
Conversation
justinpakzad
force-pushed
the
fix/datetime-serialization-fixed-offset
branch
from
October 18, 2026 00:39
2a28470 to
b22fb93
Compare
justinpakzad
marked this pull request as ready for review
October 18, 2026 00:40
This branch has not been deployed
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
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 serde timezone serializer can't handle timezones that are just a fixed offset with no name. The datetime serializer saves an empty place holder and reading the value back (e.g., via Xcom pull) fails. Take the following Dag:
On main,
do_somethingwould fail with:ValueError: ZoneInfo keys must be normalized relative paths, got:This PR adds support for timezones with a fixed, nonzero UTC offset and no name, by encoding them as a pendulum
FixedTimezone. Additional tests were added to cover the new behavior. TheNoNameTZhelper now returnsNonefrom utcoffset so thattest_timezone_serialize_no_namestill covers the fallback path (no name or fixed offset).Was generative AI tooling used to co-author this PR?
{pr_number}.significant.rst, in airflow-core/newsfragments. You can add this file in a follow-up commit after the PR is created so you know the PR number.