ZdenekSrotyr 2d6a94fb6f fix: DuckDB concurrency — WAL mode, subprocess sync, temp+rename ... Three-pronged fix for DuckDB lock conflicts: 1. WAL mode on system.duckdb — enables concurrent readers + writer 2. Sync trigger runs extractor as subprocess (not background task) — separate process = separate DuckDB connections, no lock conflict 3. Both extractor and orchestrator write to .tmp then atomic rename — avoids lock conflict with API reads on extract.duckdb/analytics.duckdb Fixes #9 permanently.		2026-03-31 13:19:57 +02:00
..
bigquery	refactor: delete old sync pipeline — 9,500 lines removed	2026-03-31 07:50:37 +02:00
jira	fix: Jira extract_init handles empty parquet dirs gracefully	2026-03-30 20:28:29 +02:00
keboola	fix: DuckDB concurrency — WAL mode, subprocess sync, temp+rename	2026-03-31 13:19:57 +02:00
llm	Suppress httpcore debug logging in LLM connector	2026-03-23 12:57:35 +01:00
openmetadata	refactor: delete old sync pipeline — 9,500 lines removed	2026-03-31 07:50:37 +02:00
__init__.py	Extract Jira into connectors/jira module	2026-03-09 11:17:50 +01:00