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

Closed
HAL9000 wants to merge 1 commits from bugfix/m3-migration-runner-check-same-thread into master

1 Commits

Author SHA1 Message Date
HAL9000 b9e37bbf9c fix(database/migration_runner): add check_same_thread=False to get_current_revision() SQLite engine
CI / benchmark-publish (pull_request) Has been skipped
CI / push-validation (pull_request) Successful in 55s
CI / security (pull_request) Failing after 1m33s
CI / benchmark-regression (pull_request) Failing after 33s
CI / helm (pull_request) Failing after 15m1s
CI / build (pull_request) Failing after 15m3s
CI / e2e_tests (pull_request) Failing after 15m3s
CI / integration_tests (pull_request) Failing after 15m6s
CI / unit_tests (pull_request) Failing after 15m8s
CI / quality (pull_request) Failing after 15m9s
CI / typecheck (pull_request) Failing after 15m9s
CI / lint (pull_request) Failing after 15m9s
CI / coverage (pull_request) Has been cancelled
CI / docker (pull_request) Has been cancelled
CI / status-check (pull_request) Has been cancelled
Pass connect_args={"check_same_thread": False} when creating a SQLite engine
in get_current_revision(), consistent with init_or_upgrade() which already
applies this setting for all SQLite engines. Without this fix, calling
get_current_revision() from a different thread than the one that created
the engine raises a ProgrammingError.

ISSUES CLOSED: #10952
2026-05-05 03:32:08 +00:00