Repository navigation
Fix async engine datetimes being shifted on non-UTC MySQL servers - #76505
Merged
vatsrahul1001 merged 1 commit intoNov 5, 2026
Merged
Conversation
jason810496
marked this pull request as ready for review
November 5, 2026 02:37
jason810496
requested review from
kaxil,
pierrejeambrun and
vatsrahul1001
and removed request for
vatsrahul1001
November 5, 2026 02:37
The async engine skipped the connection setup the sync engine gets, so its MySQL sessions kept the server time zone and stored task heartbeats and audit log rows shifted by the server's UTC offset.
jason810496
force-pushed
the
fix/db/async-engine-event-handlers
branch
from
November 5, 2026 02:42
62efed6 to
fdb4648
Compare
vatsrahul1001
enabled auto-merge (squash)
November 5, 2026 02:58
vatsrahul1001
disabled auto-merge
November 5, 2026 02:58
vatsrahul1001
approved these changes
Nov 5, 2026
Contributor
Backport successfully created: v3-4-testNote: As of Merging PRs targeted for Airflow 3.X In matter of doubt please ask in #release-management Slack channel.
|
github-actions Bot
pushed a commit
to aws-mwaa/upstream-to-airflow
that referenced
this pull request
Nov 5, 2026
… servers (apache#76505) The async engine skipped the connection setup the sync engine gets, so its MySQL sessions kept the server time zone and stored task heartbeats and audit log rows shifted by the server's UTC offset. (cherry picked from commit 494f65e) Co-authored-by: Jason(Zhe-You) Liu <68415893+jason810496@users.noreply.github.com>
aws-airflow-bot
pushed a commit
to aws-mwaa/upstream-to-airflow
that referenced
this pull request
Nov 5, 2026
… servers (apache#76505) The async engine skipped the connection setup the sync engine gets, so its MySQL sessions kept the server time zone and stored task heartbeats and audit log rows shifted by the server's UTC offset. (cherry picked from commit 494f65e) Co-authored-by: Jason(Zhe-You) Liu <68415893+jason810496@users.noreply.github.com>
Merged
1 task done
This was referenced Nov 7, 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
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.
related: #76416 (comment)
The async engine skipped the connection setup the sync engine gets, so its MySQL sessions use the server time zone and every datetime it writes or reads is shifted by the server's UTC offset. On a
+08:00MySQL 8 server, task heartbeats (async since #67800) and audit log rows (#76416) are stored 8h early. This also turns on SQLite foreign keys for async connections, matching the sync engine. To be backported tov3-4-test.Was generative AI tooling used to co-author this PR?
Generated-by: Claude Code (Opus 5.5) following the guidelines