|
Some checks failed
ci / 정본·보안·린트·타입·테스트 (push) Successful in 51s
ci / 모바일 린트·타입·Jest (push) Successful in 37s
ci / Supabase Edge Functions + Cloudflare Worker (push) Successful in 26s
ci / .NET API 서버 테스트 (push) Successful in 14s
deploy-site / deploy (push) Failing after 15s
ci / 워크스페이스 빌드 검증 (push) Failing after 11m7s
With the embedding server unavailable every chunk failed, yet the document was stored as indexed=true with 0 chunks, so the knowledge base listed it as searchable while queries could never match it. The red use-case test caught this; it had been written off as an environment failure. Now a run with zero embedded chunks leaves indexed=false and throws RAGEmbeddingFailed (surfaced by reindex, logged by addDocument). Tests that only hold on the Windows developer machine now declare it: the bundled SoX binary and PowerShell device discovery run on win32 only, and the sidecar venv test runs only when sidecar/.venv exists. The Linux Forgejo runner skips them instead of failing. |
||
|---|---|---|
| .. | ||
| ipc | ||
| services | ||
| utils | ||
| safe-filename.test.ts | ||
| suggestion-overlay-policy.test.ts | ||
| update-policy.test.ts | ||