Semantic Search recall fixture remains absent after its 120-second deadline #1415

Open
opened 2026-10-07 22:46:52 +00:00 by kayg · 0 comments
Owner

Non-blocking semantic Search finding from #1403's real release-server adversarial round. The committed attack.py creates the Apartment hunting Note (201), then expects a cross-vocabulary query to recall it within 120 seconds.

Verbatim round output:

!! DAV probe finding: semantic recall: the local model did not return 'Notes/20261007-apartment-hunting-c2593453.md' within 120s
==== FINDINGS 1
 - semantic recall :: the local model did not return 'Notes/20261007-apartment-hunting-c2593453.md' within 120s

One read-only diagnostic during the same live round, after the deadline, returned:

{"status": 200, "result_count": 0, "semantic_pending": null, "apartment_hits": []}

Query: renting a home close to public transport. Fixture body: Compare rents and neighborhoods. Check the commute and choose a home near transit.

The model readiness, opt-in configuration and embedding queue state were not recorded by this probe, so the root cause and SLOW classification are unproved. Check those conditions and the probe's path-based hit-ID matcher before changing the model or recall floor. Keep the existing regression expectation; do not raise its deadline or accept arbitrary results.

No crash, authorization failure, data corruption or sync collision is shown. The round reports the server alive and continues. This is a retrieval/verification gap, filed separately from #1411's canonical filename-query failure.

Non-blocking semantic Search finding from #1403's real release-server adversarial round. The committed `attack.py` creates the Apartment hunting Note (201), then expects a cross-vocabulary query to recall it within 120 seconds. Verbatim round output: ``` !! DAV probe finding: semantic recall: the local model did not return 'Notes/20261007-apartment-hunting-c2593453.md' within 120s ==== FINDINGS 1 - semantic recall :: the local model did not return 'Notes/20261007-apartment-hunting-c2593453.md' within 120s ``` One read-only diagnostic during the same live round, after the deadline, returned: ``` {"status": 200, "result_count": 0, "semantic_pending": null, "apartment_hits": []} ``` Query: `renting a home close to public transport`. Fixture body: `Compare rents and neighborhoods. Check the commute and choose a home near transit.` The model readiness, opt-in configuration and embedding queue state were not recorded by this probe, so the root cause and SLOW classification are unproved. Check those conditions and the probe's path-based hit-ID matcher before changing the model or recall floor. Keep the existing regression expectation; do not raise its deadline or accept arbitrary results. No crash, authorization failure, data corruption or sync collision is shown. The round reports the server alive and continues. This is a retrieval/verification gap, filed separately from #1411's canonical filename-query failure.
Commenting is not possible because the repository is archived.
No labels
No milestone
No project
No assignees
1 participant
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set

Reference
kayg/calternal-v0#1415
No description provided.