zilliztech / zilliztech/VectorDBBench
Hard-coded links in the code cause the server.baseUrlPath to fail in reverse proxy environments
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 1.2k
- Forks
- 438
- Avg merge
- 1d 4h
- Merged PRs (30d)
- 1
Description
I need to test my Milvus vector database in an offline Kubernetes cluster. Due to the lack of network installation environment, I am using the official Dockerfile to package the image and run it in the cluster. I need to access the page externally, so I have configured an Ingress with a frontend route of /mybench, and added --server.baseUrlPath /mybench in main.py. After starting, the configuration took effect, and the logs show that mybench appears in the Local URL. However, when I click on RunTest, it directly jumps to www.xxxx.com/run. Upon checking the code, I found that the jumps in frontend/components/welcome/welcomePrams.py are all hard-coded as /run.
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start with frontend/components/welcome/welcomePrams.py and main.py, reading how server.baseUrlPath is configured and how the RunTest link is assembled. Verify the application behind an Ingress at /mybench and consider the work complete when RunTest and the other welcome-page links retain that prefix instead of jumping to /run.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- frontend
- Issue type
- Bug
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Activity status
- Stale
- Clarity
- Clearly specified
- Newbie friendliness
- 62/100