This is an automated email from the ASF dual-hosted git repository.
potiuk pushed a commit to branch v3-1-test
in repository https://gitbox.apache.org/repos/asf/airflow.git
The following commit(s) were added to refs/heads/v3-1-test by this push:
new f28d275cd6b [v3-1-test] Protect against hanging thread in aiosqlite
0.22+ (#60217) (#60245)
f28d275cd6b is described below
commit f28d275cd6b6e227358d3daae4e6667962b4c2bf
Author: Jarek Potiuk <[email protected]>
AuthorDate: Wed Jan 7 23:39:40 2026 +0100
[v3-1-test] Protect against hanging thread in aiosqlite 0.22+ (#60217)
(#60245)
The change in model of aiosqlite impacted sqlalchemy handling of
closing the connection - the way how currrent sqlalchemy works
with it is that it leaves threads hanging. This is fixed
in sqlalchemy main - https://github.com/sqlalchemy/sqlalchemy/issues/13039
but until they release it and until we have the sqlalchemy>=2.0.46,
we should upper-bind the aiosqlite
(cherry picked from commit 9b364ca50ae85fe52c5e636cb3e5cc9e9f787edf)
---
airflow-core/pyproject.toml | 6 +++++-
1 file changed, 5 insertions(+), 1 deletion(-)
diff --git a/airflow-core/pyproject.toml b/airflow-core/pyproject.toml
index 9b5ece9c096..3a09090ebbc 100644
--- a/airflow-core/pyproject.toml
+++ b/airflow-core/pyproject.toml
@@ -69,7 +69,11 @@ dependencies = [
"a2wsgi>=1.10.8",
# aiosqlite 0.22.0 has a problem with hanging pytest sessions and we
excluded it
# See https://github.com/omnilib/aiosqlite/issues/369
- "aiosqlite>=0.20.0,!=0.22.0",
+ # It seems that while our test issues are fixed in 0.22.1, sqlalchemy 2
itself
+ # is not compatible with it and leaves thread hanging This is already
fixed in main of sqlalchemy
+ # But not released yet - and we will likely have to add >=2.0.46+ for
sqlalchemy when released to
+ # protect against it https://github.com/sqlalchemy/sqlalchemy/issues/13039
+ "aiosqlite>=0.20.0,<0.22.0",
# Alembic is important to handle our migrations in predictable and
performant way. It is developed
# together with SQLAlchemy. Our experience with Alembic is that it very
stable in minor version
# The 1.13.0 of alembic marked some migration code as SQLAlchemy 2+ only
so we limit it to 1.13.1
