markuseisl/mdmem
1
0 Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

Fix eval query path regressed by cleanup (results/ → eval/)

Browse Source 
The eval route was looking for queries.yaml under data_dir/results/
after Qwen's cleanup, but the spec (test + README layout) places it
at data_dir/eval/. Restores the documented path and unbreaks
test_run_eval_keeps_its_files_on_the_data_volume_and_reports_status.

Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01G9K7DZE8v1AYvfKU4qrQN5
This commit is contained in:
MarkusandClaude Sonnet 4.6 committed 2026-09-14 13:48:43 +00:00
1 parent 8fdec33037
commit c9cafc4a49
1 file changed
+1 -1
Download Patch File Download Diff File Expand all files Collapse all files
src/mdmem/ui/app.py
+1 -1
View File
@@ -627,7 +627,7 @@ def build_ui_app(svc: MemoryService) -> FastAPI: # noqa: C901 - one place, many
from mdmem.evalharness import run_eval_cli from mdmem.evalharness import run_eval_cli
data_dir = settings.index_db.parent data_dir = settings.index_db.parent
queries = data_dir / "results" / "queries.yaml" queries = data_dir / "eval" / "queries.yaml"
if not queries.exists(): if not queries.exists():
# §11: a run needs 50-100 labelled queries. Say so on the page # §11: a run needs 50-100 labelled queries. Say so on the page
# instead of starting a job that prints a hint into the log and # instead of starting a job that prints a hint into the log and