From 395728822970a7e4036bb1cfd421fd2ba120facc Mon Sep 17 00:00:00 2001 From: chopratejas Date: Sat, 25 Apr 2026 14:56:55 -0700 Subject: [PATCH] test(memory): add qdrant_url/qdrant_api_key to expected config dict The `qdrant-env-vars` change in d3c37d7 (PR #266) added `qdrant_url` and `qdrant_api_key` keys to the kwargs that `MemoryHandler` passes into `DirectMem0Adapter.__init__`. The corresponding assertion in `test_ensure_initialized_fast_paths_and_qdrant_variants` was missed in that PR and has been failing on `main` ever since. Surfacing here because it fails on every PR's CI; not caused by the Rust tokenizer work this branch adds. The two new keys are both `None` when the corresponding `HEADROOM_QDRANT_*` env vars are unset, which is the case in this test. --- tests/test_memory_handler_native_ops.py | 2 ++ 1 file changed, 2 insertions(+) diff --git a/tests/test_memory_handler_native_ops.py b/tests/test_memory_handler_native_ops.py index 982f3d0a6..c7045716f 100644 --- a/tests/test_memory_handler_native_ops.py +++ b/tests/test_memory_handler_native_ops.py @@ -1289,8 +1289,10 @@ async def test_ensure_initialized_fast_paths_and_qdrant_variants( assert qdrant_handler.initialized is True assert seen["initialized"] is True assert seen["config"] == { + "qdrant_url": None, "qdrant_host": "localhost", "qdrant_port": 6333, + "qdrant_api_key": None, "neo4j_uri": "neo4j://localhost:7687", "neo4j_user": "neo4j", "neo4j_password": "password",