Files
stack/docs
kert 90651ff004
All checks were successful
CI / lint (push) Successful in 32s
Deploy / notebooks (push) Has been skipped
Deploy / zotero (push) Has been skipped
Deploy / docs (push) Has been skipped
Deploy / api (push) Has been skipped
Deploy / mc (push) Has been skipped
Infra CI / notebooks (push) Successful in 19s
Infra CI / zotero (push) Successful in 24s
Infra CI / docs (push) Successful in 18s
Infra CI / api (push) Successful in 32s
Infra CI / mc (push) Successful in 24s
Deploy / report (push) Successful in 14s
CI / test (push) Successful in 13m22s
docs(infra): DuckDB concurrency/streaming strategy + issue-filing script
The OPPS re-ingest was blocked by a marimo notebook kernel holding a
read-only connection to the shared 3.2 GB aco.duckdb — DuckDB is
single-writer, so any open handle blocks a batch writer. This recurs for
every data-refresh workflow.

Add a strategy spec (options: preflight lock detection, notebook
read-replica, per-domain split, Iceberg lake context, DuckLake) with
milestones M1-M5, and a runnable filing script for the seven discrete
issues (no GITEA_TOKEN locally, so file with:
GITEA_TOKEN=… uv run python dev/scripts/file_concurrency_issues.py).
2026-07-08 14:53:32 -04:00
..