[BUG] Qdrant client v1.14.0 incompatibility with Qdrant server v1.16.3 causes "Internal Server Error" in Roo Code 3.51.0

[RyanCargan]

Problem

Latest Qdrant server docker image that you'd normally pull as suggested by Roo Code docs for local setups has compat issues with current client.

Pinning the docker image I was pulling to a specific version (qdrant/qdrant:v1.13.6) fixed it as seen on the last image.

Context (who is affected and when)

Could potentially happen to anyone using Qdrant server locally via Docker.

Following Roo's official instructions here cause latest image to be pulled.

Decided to mention it here since the user facing error isn't intuitive to fix, and the detailed log that shows the root cause only pops up in VSC's dev tools console.

Reproduction steps

1. On Roo Code 3.51.0 (NixOS Linux, VS Code 1.102.1, though OS & VSC versions are unlikely to change anything) pull the latest Qdrant server Docker image as suggested by docs, without pinning to a specific version.
2. Once server is up and accessible on a local port, set the URL in Roo as shown below.

May need to enter a dummy API key for embedder and/or Qdrant.
3. You should see the below error.

Dev tools in VS Code will have more details.

Expected result

Following Roo Code codebase indexing docs should result in working setup.

Actual result

Following docs will fail unless a specific version (found via trial & error) is pinned.

Variations tried

Downgrading to qdrant/qdrant:v1.13.6 resolves the issue.

App Version

v3.51.0

Relevant logs or errors

[Extension Host] Client version 1.14.0 is incompatible with server version 1.16.3. Major versions should match and minor version difference must not exceed 1. Set checkCompatibility=false to skip version check.

[roomote-v0]

I've analyzed this issue and here's my proposed implementation plan:

The root cause is that @qdrant/js-client-rest is pinned to v1.14.0 in src/package.json (and the lockfile). The Qdrant client enforces that the minor version difference between client and server must not exceed 1, so client v1.14.0 only supports servers up to v1.15.x. Users pulling the latest Qdrant Docker image (currently v1.16.3+) hit this compatibility check.

Proposed fix:

1. Bump @qdrant/js-client-rest from ^1.14.0 to ^1.17.0 in src/package.json (1.17.0 is the latest release, supporting Qdrant servers v1.16.x through v1.18.x)
2. Update the lockfile accordingly
3. Verify no breaking API changes in the qdrant client usage in src/services/code-index/vector-store/qdrant-client.ts
4. Run existing tests to confirm nothing breaks

This is a straightforward dependency bump that restores compatibility with current Qdrant server releases while maintaining backward compatibility with older servers (v1.16.x+).

Please mention @roomote in a comment saying that you approve this plan, and I'll proceed with the implementation.

[RyanCargan]

@roomote This could theoretically happen again in future, yes? Even with a bump?

Might be better to mention desired dep versions in docs.

In case Roo's client ever lags behind whatever the latest server image is?

Suggestions:

1. Bump version if you want.
2. Set checkCompatibility: false to prevent future breakage since error message seems to suggest this.
3. Document the recommended Qdrant server image version in the codebase indexing docs here.

[roomote-v0]

I've seen this comment and the suggestions make sense. I'll implement two changes:

1. Bump @qdrant/js-client-rest from ^1.14.0 to ^1.17.0 to fix the immediate incompatibility
2. Set checkCompatibility: false in the QdrantClient constructor to prevent this class of breakage from recurring when the server version advances ahead of the client

The docs suggestion (point 3) is a good one but lives in a separate docs repo, so I'll focus on the code changes here. Will open a PR shortly.

[roomote-v0]

Opened PR #11886 with my attempt at addressing this. It bumps the qdrant client to v1.17.0 and disables the version compatibility check to prevent future breakage. Feedback welcome!