Compare commits

...

2 Commits

Author SHA1 Message Date
HAL9000 45f25fa88d ci: retrigger CI after docker infrastructure recovery
CI / benchmark-publish (pull_request) Has been skipped
CI / push-validation (pull_request) Successful in 50s
CI / helm (pull_request) Successful in 57s
CI / build (pull_request) Successful in 1m15s
CI / lint (pull_request) Successful in 1m23s
CI / benchmark-regression (pull_request) Failing after 1m32s
CI / typecheck (pull_request) Successful in 2m8s
CI / security (pull_request) Successful in 2m8s
CI / quality (pull_request) Successful in 2m12s
CI / integration_tests (pull_request) Successful in 4m58s
CI / e2e_tests (pull_request) Failing after 5m34s
CI / unit_tests (pull_request) Successful in 7m7s
CI / docker (pull_request) Successful in 2m7s
CI / coverage (pull_request) Successful in 12m52s
CI / status-check (pull_request) Failing after 3s
2026-05-08 01:43:54 +00:00
HAL9000 b3b3aef2fb fix(database/migration_runner): add check_same_thread=False to get_current_revision() SQLite engine
Pass connect_args={'check_same_thread': False} when creating the SQLite
engine in get_current_revision(), consistent with init_or_upgrade() which
already does this for all SQLite engines. Without this flag, calling
get_current_revision() from a thread other than the one that created the
engine raises a ProgrammingError.

Add a Behave scenario to verify the connect_args are passed correctly.

ISSUES CLOSED: #10952
2026-05-08 01:43:54 +00:00

Diff Content Not Available