qdrant-client
Python client for Qdrant vector search engine
Runssource: GitHubhomepagePythonApache-2.0commit cf747f4b6fa7
Python, Apache-2.0 licensed. The project labels itself: qdrant, vector database, vector search and vector search engine.
qdrant-client runs. An Argusic agent installed it in 0.1 minutes and hit 3 errors and fixed every one without help on a clean machine with no GPU, and the whole session was recorded.
The qdrant-client Python library installed without errors. All local-mode tests pass. When a Qdrant server v1.19.1 runs in the same session, all REST and gRPC integration tests pass. The in-memory client creates collections, upserts points, and searches vectors successfully.
What the agent ended up with on a clean machine, in its own words. How this is measured
Measured by Argusic on a fresh machine every time. Every number links to its evidence. Argusic Score 100 of 100 (the mean of this project's run scores).
At a glance
Subject data from GitHub, linked at the top of this page, refreshed . Test data by Argusic (CC BY 4.0); every number links to a run page with the full log, the recording, and their sha256 hashes.
What was measured
From the run that decided this verdict. Every line is a recorded value, not an estimate.
What went wrong, in the agent's own words
The agent's own words, worst first, never rewritten into advice.
- Qdrant server process killed between exec sessions; tests needing server fail with connection refused unless server runs in the same exec command0.5 minutes
- test_text_match_on_unindexed_field(text_any) congruence test: local Qdrant client and server v1.19.1 differ on text-any matching against unindexed fields
- httpx/httpcore receives Errno 99 (Cannot assign requested address) when connecting to localhost due to IPv6 resolution failure in container
- Install time
- under a minute
- Cold machine to finish
- 32 minutes
- Errors hit and fixed
- 3 hit, 3 fixed with no human help
- How the result was proved
- poetry run pytest test_qdrant_client_integration (8/8 passed against Qdrant server on 127.0.0.1:6333); 58 local-mode tests passed without server; Python client created collection, upserted a point, and searched successfully in :memory: mode
- Model tokens used
- 197,236
- Exact commit tested
- cf747f4b6fa7
- Container image
- sha256:cdd920bce783
What was not measured
The other half, so you can see exactly how far this evidence goes. A gap is printed as a gap and never filled in.
- Peak GPU memory
- this ran on a CPU machine, so there was no GPU to sample
- Behaviour over a long run
- each attempt uses the smallest documented settings and a fixed time budget, so this measures whether it runs, not how it holds up under load
The end of the recording
The last lines of the terminal session that decided this verdict, exactly as they were recorded.
\" 2>&1" in /work/repo
succeeded in 1100ms:
Search result: {'city': 'NYC'}
Local mode fully functional
exec
/bin/sh -lc 'grep -n "test_text_match_on_unindexed_field" /work/repo/tests/congruence_tests/test_co…
succeeded in 0ms:
478:def test_text_match_on_unindexed_field(match: models.Match):
All evidence is collected. Here is the final result.
tokens used
197,236
All evidence is collected. Here is the final result.Replay the whole session, every command from a clean machine to this point.
How it was tested
One agent, one container, no human help. It installs the project the way its own documentation says to, runs it, and fixes what breaks. Everything below is recorded as it happened: the terminal session, the log and the exact commit. The full method.
Strengths and limits
Measured facts, not opinions. How this is written.
What went well
- Reached a running state on a clean machine, with the session recorded.
- Installed in 0.1 minutes.
- Recovered from all 3 errors without a human stepping in, which says the failures are documented well enough to solve.
- Ran without a GPU, so it does not need one to start.
- Licensed Apache-2.0, as reported by its host.
What did not, or is not known
- Measured once so far. A single attempt shows it can run, not that it runs reliably.
What it is a reasonable choice for
- Trying it on a laptop or a small server: it reached a running state without a GPU.
- A quick evaluation: it was running 0.1 minutes after the clone.
Also tested, in the same area
Every one of these was installed and run by Argusic on a clean machine. Nothing appears here that was not tested.
Run history
Topics (from GitHub)
Embed the badge
Markdown for the project README. It links back here; terms on the terms page.
[](https://argusic.com/subject/qdrant-client)Questions
- Does qdrant-client run?
- Yes. qdrant-client runs. Argusic installed and launched it on a clean machine in 0 minutes, hitting 3 errors on the way, and recorded the session.
- How did Argusic test qdrant-client?
- On a fresh, disposable machine, with every command recorded and the repository pinned at commit cf747f4b6fa7. One attempt is recorded, and the full method is on the methodology page.
- What did it cost to test qdrant-client?
- The run that produced this verdict cost $0.20: real compute and model cost, not a list price per million tokens. It is recorded on that run's page.
- How long does qdrant-client take to install?
- 0.1 minutes in the run that decided this verdict, from a clean machine to a running state. That is one measured attempt, not an average.
- Does qdrant-client need a GPU?
- Not to start. Argusic reached a running state on a machine with no GPU.
- What goes wrong when installing qdrant-client?
- 3 things broke in the recorded run, and 3 were fixed without human help. Each one, and the time it cost, is listed on this page.
- Where is the evidence for qdrant-client?
- The recorded run is on this page, each linking to its full log and terminal recording, stored with a sha256 fingerprint so it cannot be quietly altered.