zilliztech / zilliztech/VectorDBBench

Getting pydantic.errors.ConfigError: duplicate validator function while accessing Vectordbbench URL

Open
#464 6 comments 0 reactions 1 assignee View on GitHub

@alwayslove2013 is already working on this.

Since Jan 31, 2025.

Dominant language
Python
Stars
1.2k
Forks
438
Avg merge
1d 4h
Merged PRs (30d)
1

Description

Hi Team,

I have build the VectorDbBench using v0.0.21 and deployed it on pod. While accessing the Vectordbbench Url , getting below error :

Can you please suggest on that ?

pydantic.errors.ConfigError: duplicate validator function "vectordb_bench.backend.clients.api.DBConfig.not_empty_field"; if this is intended, set allow_reuse=True
Traceback:
File "/opt/code/vectordb_bench/frontend/pages/tables.py", line 2, in
from vectordb_bench.frontend.components.check_results.headerIcon import drawHeaderIcon
File "/opt/code/vectordb_bench/frontend/components/check_results/headerIcon.py", line 1, in
from vectordb_bench.frontend.config.styles import HEADER_ICON
File "/opt/code/vectordb_bench/frontend/config/styles.py", line 1, in
from vectordb_bench.models import DB
File "/opt/code/vectordb_bench/models.py", line 10, in
from .backend.cases import CaseType
File "/opt/code/vectordb_bench/backend/cases.py", line 5, in
from vectordb_bench.backend.clients.api import MetricType
File "/opt/code/vectordb_bench/backend/clients/init.py", line 3, in
from .api import (
File "/opt/code/vectordb_bench/backend/clients/api.py", line 33, in
class DBConfig(ABC, BaseModel):
File "/opt/code/vectordb_bench/backend/clients/api.py", line 66, in DBConfig
@validator("*")
^^^^^^^^^^^^^^
File "pydantic/class_validators.py", line 93, in pydantic.class_validators.validator.dec
File "pydantic/class_validators.py", line 156, in pydantic.class_validators._prepare_validator

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Assessment

This issue has not been assessed yet.

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.