fix(database/migration_runner): add check_same_thread=False to get_current_revision() SQLite engine #10967

Closed
HAL9000 wants to merge 1 commits from feature/issue-10952-fix-database-migration-runner-check-same-thread into master

1 Commits

Author SHA1 Message Date
HAL9000 6192323437 fix(database/migration_runner): add check_same_thread=False to get_current_revision() SQLite engine
CI / helm (pull_request) Failing after 50s
CI / push-validation (pull_request) Successful in 22s
CI / build (pull_request) Failing after 11m13s
CI / e2e_tests (pull_request) Failing after 11m13s
CI / integration_tests (pull_request) Failing after 11m13s
CI / unit_tests (pull_request) Failing after 11m14s
CI / quality (pull_request) Failing after 11m16s
CI / security (pull_request) Failing after 11m16s
CI / typecheck (pull_request) Failing after 11m16s
CI / lint (pull_request) Failing after 11m16s
CI / benchmark-publish (pull_request) Has been skipped
CI / benchmark-regression (pull_request) Failing after 55s
CI / coverage (pull_request) Has been cancelled
CI / docker (pull_request) Has been cancelled
CI / status-check (pull_request) Has been cancelled
MigrationRunner.get_current_revision() was creating a SQLite engine without
connect_args={"check_same_thread": False}, causing ProgrammingError when called
from a different thread than the one that created the engine. This fix makes
get_current_revision() consistent with init_or_upgrade() which already passes
check_same_thread=False for all SQLite engines.

A new Behave scenario verifies that the SQLite engine created by
get_current_revision() uses check_same_thread=False.

ISSUES CLOSED: #10952
2026-05-05 02:58:03 +00:00