[BUG]: Search Results Pagination Display Issue in VectorAdmin

[Alessandro-Pang]

How are you running VectorAdmin?

Docker (local)

What happened?

The pagination controls in VectorAdmin behave incorrectly during search operations:

• After performing a search (even when only a few results are returned), the pagination interface remains visible unnecessarily.
• Clicking on the pagination controls (e.g., page numbers or navigation buttons) has no effect when viewing search results.

Are there known steps to reproduce?

1. Perform a search query that returns fewer results than the default page size.
2. Observe the pagination controls still being displayed despite insufficient results to require pagination.
3. Attempt to click on any pagination control (e.g., "Next Page" or page numbers).

[lutuantai95]

Hi @Alessandro-Pang , Could you share with me docker-compose.yml that deploy chroma with authencation ?
Thanks in advanced!

[Alessandro-Pang]

Hi @lutuantai95,

Of course! Here's the docker-compose.yml I use — it includes Postgres and Vector Admin:

version: '3.8'

networks:
  vector_net:
    driver: bridge

services:
  db:
    image: postgres:latest
    container_name: pg_vector
    environment:
      POSTGRES_USER: vectoradmin
      POSTGRES_PASSWORD: your-db-password
      POSTGRES_DB: vdbms
    ports:
      - '5432:5432'
    volumes:
      - postgres_data:/var/lib/postgresql/data
    networks:
      - vector_net
    restart: unless-stopped

  vectoradmin:
    image: mintplexlabs/vectoradmin:latest
    container_name: vectoradmin
    depends_on:
      - db
    ports:
      - '3001:3001'
    environment:
      SERVER_PORT: '3001'
      JWT_SECRET: 'your-256-bit-secret' # 替换为随机字符串
      INNGEST_EVENT_KEY: 'background_workers'
      INNGEST_SIGNING_KEY: 'your-signing-key' # 替换为随机字符串
      INNGEST_LANDING_PAGE: 'true'
      DATABASE_CONNECTION_STRING: 'postgresql://vectoradmin:your-db-password@db:5432/vdbms'
    networks:
      - vector_net
    restart: unless-stopped

volumes:
  postgres_data:

if you happen to understand Chinese, you can check out my blog post here for more details:

https://short.pangcy.cn/u/80e385302fb43b46

You're also welcome to use a translation tool if needed.

Hope this helps!

[Alessandro-Pang]

Ah, sorry about that — I just realized my Chroma setup is deployed separately and not included in the docker-compose.yml I shared earlier.

[lutuantai95]

Ah, sorry about that — I just realized my Chroma setup is deployed separately and not included in the docker-compose.yml I shared earlier.

I got it. Have you been using Chroma Cloud or Chroma (from local docker compose) ? If it is Chroma from local docker compose, can you share it here ?

[Alessandro-Pang]

I got it. Have you been using Chroma Cloud or Chroma (from local docker compose) ? If it is Chroma from local docker compose, can you share it here ?

I'm running Chroma locally using Docker with the following command:

docker pull chromadb/chroma
docker run -p 8000:8000 chromadb/chroma

If you need authentication, please note that it was removed in v1.0 and later — you'll have to downgrade to a version below 1.0 to use it.

Relevant links:

GitHub issue: chroma-core/chroma#4288

Migration guide: https://docs.trychroma.com/docs/overview/migration#/

Hope this helps!

[lutuantai95]

I got it. Have you been using Chroma Cloud or Chroma (from local docker compose) ? If it is Chroma from local docker compose, can you share it here ?

I'm running Chroma locally using Docker with the following command:

docker pull chromadb/chroma
docker run -p 8000:8000 chromadb/chroma
If you need authentication, please note that it was removed in v1.0 and later — you'll have to downgrade to a version below 1.0 to use it.

Relevant links:

GitHub issue: chroma-core/chroma#4288

Migration guide: https://docs.trychroma.com/docs/overview/migration#/

Hope this helps!

Thanks so much for your sharing!