Fix incorrect serialisation of the FixedTimezone #38139
Merged
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.
When the
start_dateof a DAG is specified with a fixed timezone, its serialisation will not be correct and this causes the scheduler to crash.Example of an entry in the
datacolumn of the tableserialized_dagbefore fix:
{ ... "start_date": 1684684800.0, "timezone": "FixedTimezone(28800, name=\"+08:00\")", ... }after fix:
{ ... "start_date": 1684684800.0, "timezone": 28800, ... }Crash log
This issue introduced in Airflow 2.8.
^ Add meaningful description above
Read the Pull Request Guidelines for more information.
In case of fundamental code changes, an Airflow Improvement Proposal (AIP) is needed.
In case of a new dependency, check compliance with the ASF 3rd Party License Policy.
In case of backwards incompatible changes please leave a note in a newsfragment file, named
{pr_number}.significant.rstor{issue_number}.significant.rst, in newsfragments.