Merge35: semantic Search misses its apartment Note recall fixture #1468

Open
opened 2026-10-08 13:34:08 +00:00 by kayg · 1 comment
Owner

Merge35 (#1458) single real-release adversarial round reported a semantic Search recall failure. The probe does not label it SLOW, so it is filed separately rather than attributed to host load.

Exact reported shape:

!! DAV probe finding: semantic recall: the local model did not return 'Notes/<date>-apartment-hunting-<fixture-id>.md' within 120s

tests/adversarial/attack.py creates the real Note titled Apartment hunting, then queries renting a home close to public transport. The expected Note path does not enter the result set before the 120-second bound. The assertion and fixture are unchanged. Investigate embedding readiness, local model availability and result ranking; this run does not prove a cause or a data loss.

The same round separately finds the canonical NFD filename-query failure (#1464). The release upgrade probe confirms both active Search generations use the new analyzer. Product build 938a141d5, integration head 0ba15bd945. Local log: artifacts/merge35/adversarial.log.

Merge35 (#1458) single real-release adversarial round reported a semantic Search recall failure. The probe does not label it SLOW, so it is filed separately rather than attributed to host load. Exact reported shape: ``` !! DAV probe finding: semantic recall: the local model did not return 'Notes/<date>-apartment-hunting-<fixture-id>.md' within 120s ``` `tests/adversarial/attack.py` creates the real Note titled `Apartment hunting`, then queries `renting a home close to public transport`. The expected Note path does not enter the result set before the 120-second bound. The assertion and fixture are unchanged. Investigate embedding readiness, local model availability and result ranking; this run does not prove a cause or a data loss. The same round separately finds the canonical NFD filename-query failure (#1464). The release upgrade probe confirms both active Search generations use the new analyzer. Product build 938a141d5, integration head 0ba15bd9459c66dd820297474b71d603ca8e637f. Local log: `artifacts/merge35/adversarial.log`.
Author
Owner

Read-only diagnostic on the same still-running real fixture, after the reported failure:

{"exactStatus": 200, "recallStatus": 200, "fixtureCandidates": 1, "recallResults": 0, "matchesStableId": false, "matchesPathField": false, "oldIdAsPathPredicate": false}

The Note remains discoverable by exact title. The recall query returns zero results, so changing only its old ID-as-path matcher would not make this diagnostic pass. Model readiness/configuration and ranking remain unconfirmed. No probe fixture or assertion was changed.

Read-only diagnostic on the same still-running real fixture, after the reported failure: ``` {"exactStatus": 200, "recallStatus": 200, "fixtureCandidates": 1, "recallResults": 0, "matchesStableId": false, "matchesPathField": false, "oldIdAsPathPredicate": false} ``` The Note remains discoverable by exact title. The recall query returns zero results, so changing only its old ID-as-path matcher would not make this diagnostic pass. Model readiness/configuration and ranking remain unconfirmed. No probe fixture or assertion was changed.
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#1468
No description provided.