[BUG] - Codebase Indexing sends mixed-dimension embeddings to Qdrant (1536 then 4096) despite Ollama embedder config → Qdrant rejects upserts; indexing stuck at 0

[jb-brown]

Problem (one or two sentences)

When configuring Roo to use Ollama with qwen3-embedding and dimension 1536 for embeddings with Qdrant as the vector DB, Roo’s codebase indexer generates mixed embedding dimensions during a single indexing run.

Context (who is affected and when)

When setting up Codebase indexing on Ollama with qwen3-embedding, but probably with any model that isn't 4096 dimensions

Reproduction steps

When configuring Roo to use Ollama with qwen3-embedding and dimension 1536 for embeddings with Qdrant as the vector DB, Roo’s codebase indexer generates mixed embedding dimensions during a single indexing run.

• Roo creates the Qdrant collection correctly with 1536 dimensions.
• Roo successfully inserts at least one point (HTTP 200).
• Roo then repeatedly attempts to insert 4096-dimension vectors into the 1536-dimension collection.
• Qdrant rejects these inserts with a vector dimension error.
• Indexing appears stuck at or near zero due to repeated failures.

This indicates Roo is not consistently using the configured embedder for all indexing paths.

---

Environment

Host OS: macOS (Apple Silicon)
Roo: User-Agent string observed as "Roo-Code"
Ollama:

• Base URL: http://localhost:11434
• Model: qwen3-embedding:latest

Qdrant:

• Image: qdrant/qdrant:latest
• Version: 1.16.3
• Runtime: Podman
• Ports: 6333 (HTTP), 6334 (gRPC)

---

Configuration

Ollama

Embedding endpoint verified manually via HTTP request.
The endpoint returns a numeric embedding array with length 1536.

Qdrant

Qdrant URL: http://localhost:6333
Collection name created by Roo: ws-8947fbe9555f80a3

Collection configuration confirms vector size 1536 and cosine distance.

---

Steps to Reproduce

1. Start Qdrant locally.
2. Configure Roo embeddings to:
   • Provider: Ollama
   • Model: qwen3-embedding
   • Dimension: 1536
3. Start Roo workspace or codebase indexing.
4. Observe Qdrant logs during indexing.

---

Expected Behavior

Roo should always generate 1536-dimension embeddings and successfully upsert them into Qdrant.

---

Actual Behavior

Roo intermittently sends 4096-dimension vectors during indexing, which Qdrant rejects. Indexing never progresses.

---

Evidence from Logs

Successful initial operations:

• Collection creation succeeds.
• Index endpoint is called.
• First point upsert succeeds.

Repeated failures afterward:

• Qdrant logs show repeated vector dimension mismatch errors.
• HTTP 400 responses are returned for point upserts.

---

Behavior After Collection Deletion

When the collection is manually deleted, Roo continues attempting point upserts, receiving HTTP 404 responses until it recreates the collection. After recreation, the dimension mismatch resumes.

---

Qdrant Container Health (Additional Context)

Qdrant reports an unhealthy container state under Podman. Startup logs warn that the storage path is on a FUSE filesystem, which may cause data corruption. This is likely unrelated to the dimension mismatch but may affect stability.

---

Diagnosis

• Ollama qwen3-embedding consistently produces 1536-dimension vectors.
• Qdrant collection is configured for 1536.
• Roo alternates between two embedding paths:
  • One producing 1536-dimension vectors.
  • One producing 4096-dimension vectors.

Possible causes:

1. Separate embedding configuration paths for chat vs codebase indexing.
2. Silent fallback to a different embedding provider or model.
3. Cached or stale embedding configuration not fully invalidated.
4. Mixed indexing pipeline using different embedding sources.

---

Impact

Codebase indexing is effectively unusable with Ollama + Qdrant due to repeated rejected upserts. Users receive no actionable error feedback.

---

Suggested Fixes

1. Enforce a single embedding configuration for codebase indexing.
2. Validate vector dimensionality before attempting Qdrant upserts.
3. Surface clear errors to the user when dimensions mismatch.
4. Improve logging to include embedding provider, model name, and vector length.

---

Workarounds

• Configure Roo and Qdrant to use 4096 dimensions.
• Disable codebase indexing.

---

Maintainer Reproduction Checklist

• Configure Roo with Ollama qwen3-embedding and dimension 1536.
• Start indexing.
• Observe mixed vector dimensions (1536 then 4096).
• Add logging around embedding generation to identify which provider produces 4096-dimension vectors.

Expected result

codebase indexing accepts and uses the configured vector dimensions and starts indexing properly

Actual result

Codebase indexing never starts. It's always 0 / XXXX blocks.

Variations tried (optional)

No response

App Version

v3.43.0

API Provider (optional)

Ollama

Model Used (optional)

qwen3-embedding

Roo Code Task Links (optional)

No response

Relevant logs or errors (optional)

podman logs --tail=200 prosponsive-qdrant
           _                 _    
  __ _  __| |_ __ __ _ _ __ | |_  
 / _` |/ _` | '__/ _` | '_ \| __| 
| (_| | (_| | | | (_| | | | | |_  
 \__, |\__,_|_|  \__,_|_| |_|\__| 
    |_|                           

Version: 1.16.3, build: bd49f45a
Access web UI at http://localhost:6333/dashboard

2026-01-25T03:32:58.053615Z ERROR qdrant: Filesystem check failed for storage path ./storage. Details: FUSE filesystems may cause data corruption due to caching issues
2026-01-25T03:32:58.054029Z  INFO storage::content_manager::consensus::persistent: Loading raft state from ./storage/raft_state.json
2026-01-25T03:32:58.057516Z  INFO qdrant: Distributed mode disabled
2026-01-25T03:32:58.057752Z  INFO qdrant: Telemetry reporting enabled, id: 49942bcd-f432-47b5-b573-8f53a694290b
2026-01-25T03:32:58.075586Z  INFO qdrant::actix: TLS disabled for REST API
2026-01-25T03:32:58.076019Z  INFO qdrant::actix: Qdrant HTTP listening on 6333
2026-01-25T03:32:58.076097Z  INFO actix_server::builder: starting 6 workers
2026-01-25T03:32:58.076160Z  INFO actix_server::server: Actix runtime found; starting in Actix runtime
2026-01-25T03:32:58.076219Z  INFO actix_server::server: starting service: "actix-web-service-0.0.0.0:6333", workers: 6, listening on: 0.0.0.0:6333
2026-01-25T03:32:58.076810Z  INFO qdrant::tonic: Qdrant gRPC listening on 6334
2026-01-25T03:32:58.076822Z  INFO qdrant::tonic: TLS disabled for gRPC API
2026-01-27T04:41:10.150026Z  INFO actix_web::middleware::logger: 10.89.0.4 "GET /collections/ws-8947fbe9555f80a3 HTTP/1.1" 404 112 "-" "Roo-Code" 0.001154
2026-01-27T04:41:10.158935Z  INFO storage::content_manager::toc::collection_meta_ops: Creating collection ws-8947fbe9555f80a3
2026-01-27T04:41:10.172717Z  WARN memory::mmap_ops: Not using multi-mmap due to limited support, you may see reduced performance
2026-01-27T04:41:10.194741Z  INFO actix_web::middleware::logger: 10.89.0.4 "PUT /collections/ws-8947fbe9555f80a3 HTTP/1.1" 200 71 "-" "Roo-Code" 0.038438
2026-01-27T04:41:10.199133Z  INFO actix_web::middleware::logger: 10.89.0.4 "PUT /collections/ws-8947fbe9555f80a3/index HTTP/1.1" 200 94 "-" "Roo-Code" 0.002197
2026-01-27T04:41:10.201970Z  INFO actix_web::middleware::logger: 10.89.0.4 "PUT /collections/ws-8947fbe9555f80a3/index HTTP/1.1" 200 94 "-" "Roo-Code" 0.001258
2026-01-27T04:41:10.203815Z  INFO actix_web::middleware::logger: 10.89.0.4 "PUT /collections/ws-8947fbe9555f80a3/index HTTP/1.1" 200 94 "-" "Roo-Code" 0.000973
2026-01-27T04:41:10.206505Z  INFO actix_web::middleware::logger: 10.89.0.4 "PUT /collections/ws-8947fbe9555f80a3/index HTTP/1.1" 200 94 "-" "Roo-Code" 0.001092
2026-01-27T04:41:10.208783Z  INFO actix_web::middleware::logger: 10.89.0.4 "PUT /collections/ws-8947fbe9555f80a3/index HTTP/1.1" 200 95 "-" "Roo-Code" 0.001256
2026-01-27T04:41:10.210991Z  INFO actix_web::middleware::logger: 10.89.0.4 "PUT /collections/ws-8947fbe9555f80a3/index HTTP/1.1" 200 94 "-" "Roo-Code" 0.001129
2026-01-27T04:41:10.213315Z  INFO actix_web::middleware::logger: 10.89.0.4 "GET /collections/ws-8947fbe9555f80a3 HTTP/1.1" 200 435 "-" "Roo-Code" 0.000460
2026-01-27T04:41:10.559309Z  INFO actix_web::middleware::logger: 10.89.0.4 "PUT /collections/ws-8947fbe9555f80a3/points?wait=true HTTP/1.1" 200 92 "-" "Roo-Code" 0.344082
2026-01-27T04:41:27.082708Z  WARN collection::collection_manager::collection_updater: Update operation declined: Wrong input: Vector dimension error: expected dim: 1536, got 4096
2026-01-27T04:41:27.082843Z  WARN collection::shards::replica_set::update: Failed to update shard ws-8947fbe9555f80a3:0 on peer 6072079654365410, error: Wrong input: Vector dimension error: expected dim: 1536, got 4096
2026-01-27T04:41:27.083013Z  INFO actix_web::middleware::logger: 10.89.0.4 "PUT /collections/ws-8947fbe9555f80a3/points?wait=true HTTP/1.1" 400 112 "-" "Roo-Code" 0.037623
2026-01-27T04:41:42.159094Z  WARN collection::collection_manager::collection_updater: Update operation declined: Wrong input: Vector dimension error: expected dim: 1536, got 4096
2026-01-27T04:41:42.159154Z  WARN collection::shards::replica_set::update: Failed to update shard ws-8947fbe9555f80a3:0 on peer 6072079654365410, error: Wrong input: Vector dimension error: expected dim: 1536, got 4096
2026-01-27T04:41:42.159322Z  INFO actix_web::middleware::logger: 10.89.0.4 "PUT /collections/ws-8947fbe9555f80a3/points?wait=true HTTP/1.1" 400 111 "-" "Roo-Code" 0.037466
2026-01-27T04:41:54.103464Z  WARN collection::collection_manager::collection_updater: Update operation declined: Wrong input: Vector dimension error: expected dim: 1536, got 4096
2026-01-27T04:41:54.103517Z  WARN collection::shards::replica_set::update: Failed to update shard ws-8947fbe9555f80a3:0 on peer 6072079654365410, error: Wrong input: Vector dimension error: expected dim: 1536, got 4096
2026-01-27T04:41:54.103720Z  INFO actix_web::middleware::logger: 10.89.0.4 "PUT /collections/ws-8947fbe9555f80a3/points?wait=true HTTP/1.1" 400 112 "-" "Roo-Code" 0.034907
2026-01-27T04:42:10.244202Z  WARN collection::collection_manager::collection_updater: Update operation declined: Wrong input: Vector dimension error: expected dim: 1536, got 4096
2026-01-27T04:42:10.244366Z  WARN collection::shards::replica_set::update: Failed to update shard ws-8947fbe9555f80a3:0 on peer 6072079654365410, error: Wrong input: Vector dimension error: expected dim: 1536, got 4096
2026-01-27T04:42:10.244765Z  INFO actix_web::middleware::logger: 10.89.0.4 "PUT /collections/ws-8947fbe9555f80a3/points?wait=true HTTP/1.1" 400 112 "-" "Roo-Code" 0.039781
2026-01-27T04:44:11.772172Z  WARN collection::collection_manager::collection_updater: Update operation declined: Wrong input: Vector dimension error: expected dim: 1536, got 4096
2026-01-27T04:44:11.772482Z  WARN collection::shards::replica_set::update: Failed to update shard ws-8947fbe9555f80a3:0 on peer 6072079654365410, error: Wrong input: Vector dimension error: expected dim: 1536, got 4096
2026-01-27T04:44:11.773112Z  INFO actix_web::middleware::logger: 10.89.0.4 "PUT /collections/ws-8947fbe9555f80a3/points?wait=true HTTP/1.1" 400 111 "-" "Roo-Code" 0.041965
2026-01-27T04:44:28.625261Z  WARN collection::collection_manager::collection_updater: Update operation declined: Wrong input: Vector dimension error: expected dim: 1536, got 4096
2026-01-27T04:44:28.625325Z  WARN collection::shards::replica_set::update: Failed to update shard ws-8947fbe9555f80a3:0 on peer 6072079654365410, error: Wrong input: Vector dimension error: expected dim: 1536, got 4096
2026-01-27T04:44:28.625506Z  INFO actix_web::middleware::logger: 10.89.0.4 "PUT /collections/ws-8947fbe9555f80a3/points?wait=true HTTP/1.1" 400 112 "-" "Roo-Code" 0.038466
2026-01-27T04:44:43.071834Z  WARN collection::collection_manager::collection_updater: Update operation declined: Wrong input: Vector dimension error: expected dim: 1536, got 4096
2026-01-27T04:44:43.071891Z  WARN collection::shards::replica_set::update: Failed to update shard ws-8947fbe9555f80a3:0 on peer 6072079654365410, error: Wrong input: Vector dimension error: expected dim: 1536, got 4096
2026-01-27T04:44:43.072055Z  INFO actix_web::middleware::logger: 10.89.0.4 "PUT /collections/ws-8947fbe9555f80a3/points?wait=true HTTP/1.1" 400 114 "-" "Roo-Code" 0.035784
2026-01-27T04:45:41.845270Z  INFO actix_web::middleware::logger: 10.89.0.4 "GET /collections HTTP/1.1" 200 92 "-" "curl/8.7.1" 0.000150
2026-01-27T04:46:29.115941Z  WARN collection::collection_manager::collection_updater: Update operation declined: Wrong input: Vector dimension error: expected dim: 1536, got 4096
2026-01-27T04:46:29.116050Z  WARN collection::shards::replica_set::update: Failed to update shard ws-8947fbe9555f80a3:0 on peer 6072079654365410, error: Wrong input: Vector dimension error: expected dim: 1536, got 4096
2026-01-27T04:46:29.116327Z  INFO actix_web::middleware::logger: 10.89.0.4 "PUT /collections/ws-8947fbe9555f80a3/points?wait=true HTTP/1.1" 400 111 "-" "Roo-Code" 0.038190
2026-01-27T04:46:44.339185Z  WARN collection::collection_manager::collection_updater: Update operation declined: Wrong input: Vector dimension error: expected dim: 1536, got 4096
2026-01-27T04:46:44.339250Z  WARN collection::shards::replica_set::update: Failed to update shard ws-8947fbe9555f80a3:0 on peer 6072079654365410, error: Wrong input: Vector dimension error: expected dim: 1536, got 4096
2026-01-27T04:46:44.339462Z  INFO actix_web::middleware::logger: 10.89.0.4 "PUT /collections/ws-8947fbe9555f80a3/points?wait=true HTTP/1.1" 400 113 "-" "Roo-Code" 0.037111
2026-01-27T04:47:01.408834Z  INFO actix_web::middleware::logger: 10.89.0.4 "GET /collections/ws-8947fbe9555f80a3 HTTP/1.1" 200 1094 "-" "curl/8.7.1" 0.000617
2026-01-27T04:47:42.901375Z  WARN collection::collection_manager::collection_updater: Update operation declined: Wrong input: Vector dimension error: expected dim: 1536, got 4096
2026-01-27T04:47:42.901450Z  WARN collection::shards::replica_set::update: Failed to update shard ws-8947fbe9555f80a3:0 on peer 6072079654365410, error: Wrong input: Vector dimension error: expected dim: 1536, got 4096
2026-01-27T04:47:42.901694Z  INFO actix_web::middleware::logger: 10.89.0.4 "PUT /collections/ws-8947fbe9555f80a3/points?wait=true HTTP/1.1" 400 111 "-" "Roo-Code" 0.040009
2026-01-27T04:47:54.348110Z  WARN collection::collection_manager::collection_updater: Update operation declined: Wrong input: Vector dimension error: expected dim: 1536, got 4096
2026-01-27T04:47:54.348275Z  WARN collection::shards::replica_set::update: Failed to update shard ws-8947fbe9555f80a3:0 on peer 6072079654365410, error: Wrong input: Vector dimension error: expected dim: 1536, got 4096
2026-01-27T04:47:54.348466Z  INFO actix_web::middleware::logger: 10.89.0.4 "PUT /collections/ws-8947fbe9555f80a3/points?wait=true HTTP/1.1" 400 112 "-" "Roo-Code" 0.038133
2026-01-27T04:48:05.556309Z  WARN collection::collection_manager::collection_updater: Update operation declined: Wrong input: Vector dimension error: expected dim: 1536, got 4096
2026-01-27T04:48:05.556371Z  WARN collection::shards::replica_set::update: Failed to update shard ws-8947fbe9555f80a3:0 on peer 6072079654365410, error: Wrong input: Vector dimension error: expected dim: 1536, got 4096
2026-01-27T04:48:05.556576Z  INFO actix_web::middleware::logger: 10.89.0.4 "PUT /collections/ws-8947fbe9555f80a3/points?wait=true HTTP/1.1" 400 112 "-" "Roo-Code" 0.036980
2026-01-27T04:48:42.565339Z  WARN collection::collection_manager::collection_updater: Update operation declined: Wrong input: Vector dimension error: expected dim: 1536, got 4096
2026-01-27T04:48:42.565502Z  WARN collection::shards::replica_set::update: Failed to update shard ws-8947fbe9555f80a3:0 on peer 6072079654365410, error: Wrong input: Vector dimension error: expected dim: 1536, got 4096
2026-01-27T04:48:42.565697Z  INFO actix_web::middleware::logger: 10.89.0.4 "PUT /collections/ws-8947fbe9555f80a3/points?wait=true HTTP/1.1" 400 112 "-" "Roo-Code" 0.037243
2026-01-27T04:48:54.572805Z  WARN collection::collection_manager::collection_updater: Update operation declined: Wrong input: Vector dimension error: expected dim: 1536, got 4096
2026-01-27T04:48:54.572858Z  WARN collection::shards::replica_set::update: Failed to update shard ws-8947fbe9555f80a3:0 on peer 6072079654365410, error: Wrong input: Vector dimension error: expected dim: 1536, got 4096
2026-01-27T04:48:54.573016Z  INFO actix_web::middleware::logger: 10.89.0.4 "PUT /collections/ws-8947fbe9555f80a3/points?wait=true HTTP/1.1" 400 112 "-" "Roo-Code" 0.038537
2026-01-27T04:49:05.555518Z  WARN collection::collection_manager::collection_updater: Update operation declined: Wrong input: Vector dimension error: expected dim: 1536, got 4096
2026-01-27T04:49:05.555587Z  WARN collection::shards::replica_set::update: Failed to update shard ws-8947fbe9555f80a3:0 on peer 6072079654365410, error: Wrong input: Vector dimension error: expected dim: 1536, got 4096
2026-01-27T04:49:05.555760Z  INFO actix_web::middleware::logger: 10.89.0.4 "PUT /collections/ws-8947fbe9555f80a3/points?wait=true HTTP/1.1" 400 112 "-" "Roo-Code" 0.037123
2026-01-27T04:49:43.494255Z  WARN collection::collection_manager::collection_updater: Update operation declined: Wrong input: Vector dimension error: expected dim: 1536, got 4096
2026-01-27T04:49:43.494309Z  WARN collection::shards::replica_set::update: Failed to update shard ws-8947fbe9555f80a3:0 on peer 6072079654365410, error: Wrong input: Vector dimension error: expected dim: 1536, got 4096
2026-01-27T04:49:43.494467Z  INFO actix_web::middleware::logger: 10.89.0.4 "PUT /collections/ws-8947fbe9555f80a3/points?wait=true HTTP/1.1" 400 113 "-" "Roo-Code" 0.035691
2026-01-27T04:49:54.782504Z  WARN collection::collection_manager::collection_updater: Update operation declined: Wrong input: Vector dimension error: expected dim: 1536, got 4096
2026-01-27T04:49:54.782575Z  WARN collection::shards::replica_set::update: Failed to update shard ws-8947fbe9555f80a3:0 on peer 6072079654365410, error: Wrong input: Vector dimension error: expected dim: 1536, got 4096
2026-01-27T04:49:54.782742Z  INFO actix_web::middleware::logger: 10.89.0.4 "PUT /collections/ws-8947fbe9555f80a3/points?wait=true HTTP/1.1" 400 112 "-" "Roo-Code" 0.034771
2026-01-27T04:50:05.957173Z  WARN collection::collection_manager::collection_updater: Update operation declined: Wrong input: Vector dimension error: expected dim: 1536, got 4096
2026-01-27T04:50:05.957234Z  WARN collection::shards::replica_set::update: Failed to update shard ws-8947fbe9555f80a3:0 on peer 6072079654365410, error: Wrong input: Vector dimension error: expected dim: 1536, got 4096
2026-01-27T04:50:05.957413Z  INFO actix_web::middleware::logger: 10.89.0.4 "PUT /collections/ws-8947fbe9555f80a3/points?wait=true HTTP/1.1" 400 114 "-" "Roo-Code" 0.035342
2026-01-27T04:50:27.677864Z  WARN collection::collection_manager::collection_updater: Update operation declined: Wrong input: Vector dimension error: expected dim: 1536, got 4096
2026-01-27T04:50:27.677926Z  WARN collection::shards::replica_set::update: Failed to update shard ws-8947fbe9555f80a3:0 on peer 6072079654365410, error: Wrong input: Vector dimension error: expected dim: 1536, got 4096
2026-01-27T04:50:27.678112Z  INFO actix_web::middleware::logger: 10.89.0.4 "PUT /collections/ws-8947fbe9555f80a3/points?wait=true HTTP/1.1" 400 112 "-" "Roo-Code" 0.039326
2026-01-27T04:51:27.920879Z  WARN collection::collection_manager::collection_updater: Update operation declined: Wrong input: Vector dimension error: expected dim: 1536, got 4096
2026-01-27T04:51:27.920986Z  WARN collection::shards::replica_set::update: Failed to update shard ws-8947fbe9555f80a3:0 on peer 6072079654365410, error: Wrong input: Vector dimension error: expected dim: 1536, got 4096
2026-01-27T04:51:27.921325Z  INFO actix_web::middleware::logger: 10.89.0.4 "PUT /collections/ws-8947fbe9555f80a3/points?wait=true HTTP/1.1" 400 114 "-" "Roo-Code" 0.040893
2026-01-27T04:51:55.614439Z  INFO actix_web::middleware::logger: 10.89.0.4 "POST /collections/ws-8947fbe9555f80a3/points/query HTTP/1.1" 400 113 "-" "Roo-Code" 0.002493
2026-01-27T04:52:00.769240Z  INFO storage::content_manager::toc::collection_meta_ops: Deleting collection ws-8947fbe9555f80a3
2026-01-27T04:52:00.788301Z  INFO actix_web::middleware::logger: 10.89.0.4 "DELETE /collections/ws-8947fbe9555f80a3 HTTP/1.1" 200 47 "-" "curl/8.7.1" 0.019230
2026-01-27T04:52:28.399893Z  INFO actix_web::middleware::logger: 10.89.0.4 "PUT /collections/ws-8947fbe9555f80a3/points?wait=true HTTP/1.1" 404 114 "-" "Roo-Code" 0.032821
2026-01-27T04:53:25.180129Z  INFO actix_web::middleware::logger: 10.89.0.4 "PUT /collections/ws-8947fbe9555f80a3/points?wait=true HTTP/1.1" 404 113 "-" "Roo-Code" 0.033801
2026-01-27T04:53:33.106488Z  INFO actix_web::middleware::logger: 10.89.0.4 "PUT /collections/ws-8947fbe9555f80a3/points?wait=true HTTP/1.1" 404 114 "-" "Roo-Code" 0.033613
2026-01-27T04:53:40.988180Z  INFO actix_web::middleware::logger: 10.89.0.4 "PUT /collections/ws-8947fbe9555f80a3/points?wait=true HTTP/1.1" 404 114 "-" "Roo-Code" 0.037162
2026-01-27T04:53:48.841549Z  INFO actix_web::middleware::logger: 10.89.0.4 "PUT /collections/ws-8947fbe9555f80a3/points?wait=true HTTP/1.1" 404 113 "-" "Roo-Code" 0.033731
2026-01-27T04:53:56.607568Z  INFO actix_web::middleware::logger: 10.89.0.4 "PUT /collections/ws-8947fbe9555f80a3/points?wait=true HTTP/1.1" 404 114 "-" "Roo-Code" 0.035077
2026-01-27T04:54:03.632205Z  INFO actix_web::middleware::logger: 10.89.0.4 "PUT /collections/ws-8947fbe9555f80a3/points?wait=true HTTP/1.1" 404 115 "-" "Roo-Code" 0.033169
2026-01-27T04:54:11.242297Z  INFO actix_web::middleware::logger: 10.89.0.4 "PUT /collections/ws-8947fbe9555f80a3/points?wait=true HTTP/1.1" 404 114 "-" "Roo-Code" 0.032851
2026-01-27T04:54:24.961069Z  INFO actix_web::middleware::logger: 10.89.0.4 "PUT /collections/ws-8947fbe9555f80a3/points?wait=true HTTP/1.1" 404 115 "-" "Roo-Code" 0.031479
2026-01-27T04:54:32.537724Z  INFO actix_web::middleware::logger: 10.89.0.4 "PUT /collections/ws-8947fbe9555f80a3/points?wait=true HTTP/1.1" 404 114 "-" "Roo-Code" 0.032509
2026-01-27T04:54:40.468327Z  INFO actix_web::middleware::logger: 10.89.0.4 "PUT /collections/ws-8947fbe9555f80a3/points?wait=true HTTP/1.1" 404 114 "-" "Roo-Code" 0.031746
2026-01-27T04:54:48.167580Z  INFO actix_web::middleware::logger: 10.89.0.4 "PUT /collections/ws-8947fbe9555f80a3/points?wait=true HTTP/1.1" 404 114 "-" "Roo-Code" 0.030854
2026-01-27T04:54:56.180634Z  INFO actix_web::middleware::logger: 10.89.0.4 "PUT /collections/ws-8947fbe9555f80a3/points?wait=true HTTP/1.1" 404 114 "-" "Roo-Code" 0.032397
2026-01-27T04:55:03.128107Z  INFO actix_web::middleware::logger: 10.89.0.4 "PUT /collections/ws-8947fbe9555f80a3/points?wait=true HTTP/1.1" 404 114 "-" "Roo-Code" 0.032719
2026-01-27T04:55:10.916527Z  INFO actix_web::middleware::logger: 10.89.0.4 "PUT /collections/ws-8947fbe9555f80a3/points?wait=true HTTP/1.1" 404 114 "-" "Roo-Code" 0.033368
2026-01-27T04:55:25.519682Z  INFO actix_web::middleware::logger: 10.89.0.4 "PUT /collections/ws-8947fbe9555f80a3/points?wait=true HTTP/1.1" 404 113 "-" "Roo-Code" 0.031954
2026-01-27T04:55:33.096155Z  INFO actix_web::middleware::logger: 10.89.0.4 "PUT /collections/ws-8947fbe9555f80a3/points?wait=true HTTP/1.1" 404 113 "-" "Roo-Code" 0.033385
2026-01-27T04:55:40.699082Z  INFO actix_web::middleware::logger: 10.89.0.4 "PUT /collections/ws-8947fbe9555f80a3/points?wait=true HTTP/1.1" 404 113 "-" "Roo-Code" 0.032578
2026-01-27T04:55:48.174333Z  INFO actix_web::middleware::logger: 10.89.0.4 "PUT /collections/ws-8947fbe9555f80a3/points?wait=true HTTP/1.1" 404 115 "-" "Roo-Code" 0.030315
2026-01-27T04:55:55.977846Z  INFO actix_web::middleware::logger: 10.89.0.4 "PUT /collections/ws-8947fbe9555f80a3/points?wait=true HTTP/1.1" 404 114 "-" "Roo-Code" 0.035475
2026-01-27T04:56:03.036025Z  INFO actix_web::middleware::logger: 10.89.0.4 "PUT /collections/ws-8947fbe9555f80a3/points?wait=true HTTP/1.1" 404 114 "-" "Roo-Code" 0.031710
2026-01-27T04:56:10.712311Z  INFO actix_web::middleware::logger: 10.89.0.4 "PUT /collections/ws-8947fbe9555f80a3/points?wait=true HTTP/1.1" 404 114 "-" "Roo-Code" 0.033532
2026-01-27T04:56:17.991312Z  INFO actix_web::middleware::logger: 10.89.0.4 "PUT /collections/ws-8947fbe9555f80a3/points?wait=true HTTP/1.1" 404 115 "-" "Roo-Code" 0.030619
2026-01-27T04:56:25.335927Z  INFO actix_web::middleware::logger: 10.89.0.4 "PUT /collections/ws-8947fbe9555f80a3/points?wait=true HTTP/1.1" 404 115 "-" "Roo-Code" 0.032366
2026-01-27T04:57:25.632889Z  INFO actix_web::middleware::logger: 10.89.0.4 "PUT /collections/ws-8947fbe9555f80a3/points?wait=true HTTP/1.1" 404 114 "-" "Roo-Code" 0.033023
2026-01-27T04:58:08.292559Z  INFO actix_web::middleware::logger: 10.89.0.4 "GET /collections/ws-8947fbe9555f80a3 HTTP/1.1" 404 109 "-" "Roo-Code" 0.000182
2026-01-27T04:58:08.294840Z  INFO storage::content_manager::toc::collection_meta_ops: Creating collection ws-8947fbe9555f80a3
2026-01-27T04:58:08.328287Z  INFO actix_web::middleware::logger: 10.89.0.4 "PUT /collections/ws-8947fbe9555f80a3 HTTP/1.1" 200 71 "-" "Roo-Code" 0.033611
2026-01-27T04:58:08.331689Z  INFO actix_web::middleware::logger: 10.89.0.4 "PUT /collections/ws-8947fbe9555f80a3/index HTTP/1.1" 200 94 "-" "Roo-Code" 0.001464
2026-01-27T04:58:08.334157Z  INFO actix_web::middleware::logger: 10.89.0.4 "PUT /collections/ws-8947fbe9555f80a3/index HTTP/1.1" 200 94 "-" "Roo-Code" 0.001260
2026-01-27T04:58:08.336548Z  INFO actix_web::middleware::logger: 10.89.0.4 "PUT /collections/ws-8947fbe9555f80a3/index HTTP/1.1" 200 93 "-" "Roo-Code" 0.001333
2026-01-27T04:58:08.338916Z  INFO actix_web::middleware::logger: 10.89.0.4 "PUT /collections/ws-8947fbe9555f80a3/index HTTP/1.1" 200 94 "-" "Roo-Code" 0.001235
2026-01-27T04:58:08.341431Z  INFO actix_web::middleware::logger: 10.89.0.4 "PUT /collections/ws-8947fbe9555f80a3/index HTTP/1.1" 200 95 "-" "Roo-Code" 0.001494
2026-01-27T04:58:08.344003Z  INFO actix_web::middleware::logger: 10.89.0.4 "PUT /collections/ws-8947fbe9555f80a3/index HTTP/1.1" 200 95 "-" "Roo-Code" 0.001304
2026-01-27T04:58:08.346149Z  INFO actix_web::middleware::logger: 10.89.0.4 "GET /collections/ws-8947fbe9555f80a3 HTTP/1.1" 200 433 "-" "Roo-Code" 0.000272
2026-01-27T04:58:08.660197Z  INFO actix_web::middleware::logger: 10.89.0.4 "PUT /collections/ws-8947fbe9555f80a3/points?wait=true HTTP/1.1" 200 91 "-" "Roo-Code" 0.312472
2026-01-27T04:58:28.123740Z  WARN collection::collection_manager::collection_updater: Update operation declined: Wrong input: Vector dimension error: expected dim: 1536, got 4096
2026-01-27T04:58:28.123822Z  WARN collection::shards::replica_set::update: Failed to update shard ws-8947fbe9555f80a3:0 on peer 6072079654365410, error: Wrong input: Vector dimension error: expected dim: 1536, got 4096
2026-01-27T04:58:28.124016Z  INFO actix_web::middleware::logger: 10.89.0.4 "PUT /collections/ws-8947fbe9555f80a3/points?wait=true HTTP/1.1" 400 112 "-" "Roo-Code" 0.058895
2026-01-27T04:58:45.673221Z  WARN collection::collection_manager::collection_updater: Update operation declined: Wrong input: Vector dimension error: expected dim: 1536, got 4096
2026-01-27T04:58:45.673402Z  WARN collection::shards::replica_set::update: Failed to update shard ws-8947fbe9555f80a3:0 on peer 6072079654365410, error: Wrong input: Vector dimension error: expected dim: 1536, got 4096
2026-01-27T04:58:45.673571Z  INFO actix_web::middleware::logger: 10.89.0.4 "PUT /collections/ws-8947fbe9555f80a3/points?wait=true HTTP/1.1" 400 112 "-" "Roo-Code" 0.053522
2026-01-27T04:59:01.326241Z  WARN collection::collection_manager::collection_updater: Update operation declined: Wrong input: Vector dimension error: expected dim: 1536, got 4096
2026-01-27T04:59:01.326297Z  WARN collection::shards::replica_set::update: Failed to update shard ws-8947fbe9555f80a3:0 on peer 6072079654365410, error: Wrong input: Vector dimension error: expected dim: 1536, got 4096
2026-01-27T04:59:01.326439Z  INFO actix_web::middleware::logger: 10.89.0.4 "PUT /collections/ws-8947fbe9555f80a3/points?wait=true HTTP/1.1" 400 112 "-" "Roo-Code" 0.035439

[roomote]

I've analyzed this issue and identified the root cause.

Root Cause Analysis

The issue occurs because there's a mismatch between the user-configured embedding dimension and the actual dimension produced by the Ollama model:

1. User configures dimension as 1536 in Roo Code settings for qwen3-embedding
2. Qdrant collection is created with 1536 dimensions based on this configuration
3. First upsert succeeds - This is actually a metadata marker point using new Array(vectorSize).fill(0) (see qdrant-client.ts:markIndexingIncomplete()) which uses the configured dimension
4. Subsequent upserts fail - The actual embeddings from Ollama's qwen3-embedding model are 4096 dimensions, not 1536

The qwen3-embedding model isn't in Roo Code's EMBEDDING_MODEL_PROFILES for Ollama, so it falls back to using the manually configured dimension. However, Roo Code never validates that the actual embedding output matches this configured dimension.

Proposed Implementation Plan

1. Add Embedding Dimension Validation (Primary Fix)

Modify the embedder validation logic to check that the actual embedding dimensions match the expected dimensions:

• Update CodeIndexOllamaEmbedder.validateConfiguration() to capture and return the actual embedding dimension from the test embedding
• Update CodeIndexServiceFactory.validateEmbedder() to compare the actual dimension against the expected dimension and return a clear error if they don't match
• This ensures users get immediate feedback when their configured dimension is incorrect

2. Add Popular Ollama Embedding Models to Profiles

Add common Ollama embedding models to EMBEDDING_MODEL_PROFILES:

ollama: {
    // Existing models...
    "qwen3-embedding:latest": { dimension: 4096, scoreThreshold: 0.4 },
    "qwen3-embedding-0.6b": { dimension: 1024, scoreThreshold: 0.4 },
    "qwen3-embedding-4b": { dimension: 2560, scoreThreshold: 0.4 },
    "qwen3-embedding-8b": { dimension: 4096, scoreThreshold: 0.4 },
}

3. Improve Error Messaging

When dimension mismatch is detected:

• Display a clear, actionable error: "Embedding dimension mismatch: expected {configured} but model produced {actual}. Please update your dimension setting to {actual}."
• Include the model name in the error for debugging

Benefits

• Immediate feedback: Users know right away if their dimension config is wrong
• Prevents silent failures: No more stuck indexing at 0/XXXX
• Better UX: Clear guidance on how to fix the issue

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

[jb-brown]

After updating to 4096 and restarting VSCode this started working. But wasn't clear at all what was happening, why, or what to do about it. I didn't question the deminsions that ChatGPT told me but should have.

[jb-brown]

@roomote Is there any value of having the user enter the dimensions value if it can be determined programmatically? If there wasn't a user supplied value the descrepency couldn't exist.

[roomote]

Great question! Auto-detecting the embedding dimension programmatically would indeed eliminate this class of errors entirely.

I'll explore implementing this enhancement:

1. During embedder validation, generate a test embedding
2. Capture the actual dimension from the returned embedding
3. Use the auto-detected dimension instead of requiring manual user input

This would make the dimension field optional (or hidden) and always use the correct value from the model itself. I'll open a PR to share progress on this approach.

[roomote]

Implementation Complete

I have implemented the auto-detection of embedding dimensions as suggested by @jb-brown.

PR: #10993

Summary of Changes

The system now automatically detects embedding dimensions during validation by parsing the test embedding response. This eliminates the need for users to manually configure dimensions and prevents mismatches between configured and actual dimensions.

Key changes:

1. All 8 embedders now return detectedDimension from their validateConfiguration() method

2. The detected dimension is prioritized over profile-based and manual configuration:

   • Priority 1: Auto-detected from test embedding (most reliable)
   • Priority 2: Profile-based from getModelDimension()
   • Priority 3: Manual configuration from modelDimension setting

3. For Ollama specifically, the dimension is extracted from the /api/embed test response which already runs during validation

This should resolve the issue where users configure 1536 dimensions but models like qwen3-embedding actually produce 4096-dimension embeddings.