[Tests] Extend semantic_memory_smoke with edge case coverage
Nobody has claimed this yet.
Assessment
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Newbie friendliness
- 58/100
Research direction
Read tools/longmemeval-mini/semantic_memory_smoke.py and semantic_memory_smoke_extended.py to compare the existing basic and extended coverage. Add the four named edge-case tests, define and document expected behavior for each, and verify the smoke tests cover empty, corrupted, Unicode, and very long memory data.
Written by the indexing model from the issue text.
Description
Summary
The semantic memory smoke tests need additional edge case coverage.
Current State
semantic_memory_smoke.py: 3 basic testssemantic_memory_smoke_extended.py: 17 extended tests- Tests focus on "happy path" scenarios
Missing Edge Cases
- Empty memory file handling: Query with empty
.memfile - Corrupted memory file: Handle truncated or invalid embedding rows
- Unicode/UTF-8 edge cases: Facts with multi-byte characters
- Very long facts: Facts exceeding typical token limits
- Concurrent access: Multiple processes accessing same memory file
- Memory file permissions: Read-only filesystem scenarios
Acceptance Criteria
- Add
test_empty_memory_query- verify graceful handling - Add
test_corrupted_memory_recovery- validate error messages - Add
test_unicode_fact_storage- UTF-8 roundtrip - Add
test_very_long_fact_truncation- document behavior - Document expected behavior for each edge case
Related Files
tools/longmemeval-mini/semantic_memory_smoke.pytools/longmemeval-mini/semantic_memory_smoke_extended.py
- Dominant language
- C++
- Stars
- 1
- Forks
- 0
- PR merge metrics
- No merged PRs in 30d
Getting set up
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from jose-compu/funes.cpp
-
stale
Difficulty 5/5 Over a week Newbie friendliness 25/100
jose-compu/funes.cpp#12 ·
-
stale
Difficulty 4/5 3-5 days Newbie friendliness 52/100
jose-compu/funes.cpp#11 ·
-
stale
Difficulty 4/5 3-5 days Newbie friendliness 48/100
jose-compu/funes.cpp#10 ·
-
stale
Difficulty 4/5 3-5 days Newbie friendliness 55/100
jose-compu/funes.cpp#9 ·
-
stale
Difficulty 4/5 3-5 days Newbie friendliness 45/100
jose-compu/funes.cpp#8 ·
All issues in jose-compu/funes.cpp
Similar issues
-
area/actorsystem bug tsan
Difficulty 2/5 1-3 hours Newbie friendliness 74/100
ydb-platform/ydb#54282 ·
Maintainers usually reply within 1 day
-
bug needs triage
Difficulty 1/5 Under an hour Newbie friendliness 90/100
project-chip/connectedhomeip#74434 ·
Maintainers usually reply within 1 day
-
Difficulty 1/5 Under an hour Newbie friendliness 88/100
tenstorrent/tt-metal#58057 · 1 comment ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 84/100
maplibre/maplibre-native#4690 ·
Maintainers usually reply within 1 day
-
comp-query-execution
Difficulty 2/5 1-3 hours Newbie friendliness 84/100
ClickHouse/ClickHouse#122569 ·
Maintainers usually reply within 1 day