vatsrahul1001 opened a new pull request, #67470: URL: https://github.com/apache/airflow/pull/67470
Manual backport of #67467 — auto-backport failed (https://github.com/apache/airflow/actions/runs/26402200482). ## Why auto-backport failed Conflict in `uv.lock` on the `secretstorage` package — its dependency markers diverged between main and v3-2-test (main has more complex Python-3.14 / emscripten / win32 markers; v3-2-test has the simpler old form). Unrelated to the actual pymysql fix. ## Resolution Kept v3-2-test's simpler `secretstorage` markers (consistent with the rest of v3-2-test's lock). Then re-ran `uv lock` to enforce the new `pymysql>=1.0.3,<1.2` constraint — pymysql resolved to 1.1.3 in the lock, no other transitive drift. ## What this fixes Unblocks the MySQL `test_async_session` failures we've been hitting on v3-2-test backport PRs (#67460, #67466). Root cause was today's `constraints-3-2` auto-update bumping PyMySQL 1.1.3 → 1.2.0, which broke `AsyncAdapt_aiomysql_connection.ping()` via SQLAlchemy 1.4 downgrade (triggered by `databricks-sqlalchemy<2.0`). ## Test plan - [X] Cherry-picked with `-x` trailer (preserves provenance reference to 7ea8362c55) - [X] Conflict resolved (secretstorage markers only) - [X] `uv lock` regenerated — pymysql pinned at 1.1.3, ~20 lines of lock diff - [ ] Watch CI on v3-2-test (especially the MySQL Core...Serialization jobs that have been failing) - [ ] After merge: re-run CI on #67460 and #67466 to confirm they go green -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected]
