Laurent Wandrebeck
cdcfc3c218
The rust lib suite shares extensive process-global state (env vars, the data-dir singleton, the context-os runtime, the search-delta tracker, process-group probes, ann-cache, shell-allowlist, ...). It is green single-threaded but flakes intermittently under cargo's default parallel harness. The main CI test jobs already pass '-- --test-threads=1' for this reason; align the remaining entry points: - pull_request_template.md: the test-plan checklist now runs serialized - dep-update.yml: the rust 'cargo test' step runs serialized (A developer-local rust/.cargo/config.toml with RUST_TEST_THREADS=1 — gitignored by the project — makes a bare 'cargo test' behave the same.) Also harden ContextBus::open_read_conn to create the DB parent dir before opening (matching open_at), so a lazily-opened read connection can't panic if the data dir was removed underneath the process-global runtime. Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
807 B
807 B
Summary
What does this PR change and why?
Test plan
cd rust && cargo test -- --test-threads=1(the suite shares process-global state; CI serializes it too)cd rust && cargo clippy --all-targets --all-features -- -D warningscd rust && cargo fmt --check- If cookbook/packages changed: relevant
npm test/ build steps
Notes for reviewers
- Risk areas / edge cases:
- Backwards compatibility:
- Docs updated (links/files):
Contributor License Agreement
First-time contributors: a bot will ask you to sign our one-time
CLA (it keeps lean-ctx
Apache-2.0 and free for individual developers — see §8). You sign once by
replying to this PR with: I have read the CLA Document and I hereby sign the CLA