~95% on SimpleQA (e.g. Qwen3.6-27B on a 3090). Supports all local and cloud LLMs (llama.cpp, Ollama, Google, ...). 10+ search engines - arXiv, PubMed, your private documents. Everything Local & Encrypted.
Notes concurrency release check
notes-concurrency.yml runs before release publication and can also be started
manually from GitHub Actions. It does not run on ordinary pull requests. A failure,
cancellation, or skipped probe blocks the release build.
The probes hold synchronous model cleanup or rate-limit storage open and require an unrelated request to complete before that work is released. An independent watchdog records a failure before unblocking stalled work, so event-loop recovery cannot turn a stall into a pass. The assertions cover:
- Owned models receive exactly one cleanup attempt after success, failure, or cancellation, and the request waits for cleanup to finish.
- A registered shared model stays usable across requests and remains owned by its registering caller.
- An unrelated request completes while cleanup or rate-limit storage is held.
- The notes AI quota allows ten requests, rejects the next with HTTP 429, and gives another user a separate quota.
- Deliberately blocking or removing cleanup, or disabling rate limiting, is rejected by the assertions themselves.
The probes use controlled local dependencies and require no model credentials or Redis server. Elapsed times are diagnostics, not tight performance thresholds. They exercise application cleanup ownership; native provider shutdown remains provider-specific. The release selection also includes a direct service cancellation test that requires pending cleanup to finish before cancellation propagates.
After installing the development dependencies, run the release suite locally:
LDR_TESTING_WITH_MOCKS=false LDR_DISABLE_RATE_LIMITING=false \
pdm run pytest tests/integration/test_notes_release_concurrency.py \
tests/notes/test_note_ai_service.py::TestNoteAIServiceAsyncTeardownAndOffload::test_cancellation_during_cleanup_waits_for_worker \
-n 0 -p no:cov -v --tb=short --timeout=60
Run it serially without coverage, as in the release workflow. The integration
marker keeps these deliberate blocking probes out of the ordinary mocked suite;
LDR_TESTING_WITH_MOCKS=false ensures they execute. The workflow independently
rejects missing, empty, skipped, or unsuccessful JUnit results, and preserves the
JUnit report and pytest output in the notes-concurrency-results artifact for
14 days, including failed runs.
The fast workflow contract tests run with the ordinary suite:
pdm run pytest tests/ci/test_notes_concurrency_release_gate.py -n 0 -p no:cov