langgenius/dify
1
0
Fork 0
mirror of https://github.com/langgenius/dify.git synced 2026-07-21 20:15:31 -04:00
Code Issues 775 Packages Projects Releases 10 Wiki Activity

Error in line TIDB_ON_QDRANT_CLIENT_TIMEOUT: ${TIDB_ON_QDRANT_API_KEY:-20} #6427

New Issue
Closed
opened 2026-02-21 18:15:42 -05:00 by yindo · 3 comments
yindo commented 2026-02-21 18:15:42 -05:00
Owner
Copy Link
Copy Source

Originally created by @Eyal51 on GitHub (Oct 29, 2024).

Self Checks

  • This is only for bug report, if you would like to ask a question, please head to Discussions.
  • I have searched for existing issues search for existing issues, including closed ones.
  • I confirm that I am using English to submit this report (我已阅读并同意 Language Policy).
  • [FOR CHINESE USERS] 请务必使用英文提交 Issue，否则会被关闭。谢谢！:）
  • Please do not modify this template :) and fill in all the required fields.

Dify version

1.10

Cloud or Self Hosted

Self Hosted (Docker)

Steps to reproduce

docker compose didn't work because this line on docker-compose.yaml
TIDB_ON_QDRANT_CLIENT_TIMEOUT: ${TIDB_ON_QDRANT_API_KEY:-20}
i changed it to 20 and it works.

✔️ Expected Behavior

No response

❌ Actual Behavior

No response

Originally created by @Eyal51 on GitHub (Oct 29, 2024). ### Self Checks - [X] This is only for bug report, if you would like to ask a question, please head to [Discussions](https://github.com/langgenius/dify/discussions/categories/general). - [X] I have searched for existing issues [search for existing issues](https://github.com/langgenius/dify/issues), including closed ones. - [X] I confirm that I am using English to submit this report (我已阅读并同意 [Language Policy](https://github.com/langgenius/dify/issues/1542)). - [X] [FOR CHINESE USERS] 请务必使用英文提交 Issue，否则会被关闭。谢谢！:） - [X] Please do not modify this template :) and fill in all the required fields. ### Dify version 1.10 ### Cloud or Self Hosted Self Hosted (Docker) ### Steps to reproduce docker compose didn't work because this line on docker-compose.yaml ``` TIDB_ON_QDRANT_CLIENT_TIMEOUT: ${TIDB_ON_QDRANT_API_KEY:-20}``` i changed it to `20` and it works. ### ✔️ Expected Behavior _No response_ ### ❌ Actual Behavior _No response_
yindo added the 👻 feat:rag label 2026-02-21 18:15:42 -05:00
yindo closed this issue 2026-02-21 18:15:42 -05:00
yindo commented 2026-02-21 18:15:42 -05:00
Author
Owner
Copy Link
Copy Source

@dosubot[bot] commented on GitHub (Oct 29, 2024):

@Eyal51 Hello! I'm here to help you with any bugs, questions, or contributions. Let's tackle this together while we wait for a human maintainer.

The error you're encountering is due to a misconfiguration in the docker-compose.yaml file. The line:

TIDB_ON_QDRANT_CLIENT_TIMEOUT: ${TIDB_ON_QDRANT_API_KEY:-20}

is incorrect because it uses the wrong environment variable. The TIDB_ON_QDRANT_CLIENT_TIMEOUT should be set to a timeout value, not the API key. It should look like this:

TIDB_ON_QDRANT_CLIENT_TIMEOUT: ${TIDB_ON_QDRANT_CLIENT_TIMEOUT:-20}

This sets the TIDB_ON_QDRANT_CLIENT_TIMEOUT to the value of the environment variable TIDB_ON_QDRANT_CLIENT_TIMEOUT if it is set, or defaults to 20 seconds if it is not set. Make sure to update your docker-compose.yaml file accordingly.

To continue talking to Dosu, mention @dosu.

@dosubot[bot] commented on GitHub (Oct 29, 2024): <!-- Greeting --> @Eyal51 Hello! I'm here to help you with any bugs, questions, or contributions. Let's tackle this together while we wait for a human maintainer. <!-- Answer --> The error you're encountering is due to a misconfiguration in the `docker-compose.yaml` file. The line: ```yaml TIDB_ON_QDRANT_CLIENT_TIMEOUT: ${TIDB_ON_QDRANT_API_KEY:-20} ``` is incorrect because it uses the wrong environment variable. The `TIDB_ON_QDRANT_CLIENT_TIMEOUT` should be set to a timeout value, not the API key. It should look like this: ```yaml TIDB_ON_QDRANT_CLIENT_TIMEOUT: ${TIDB_ON_QDRANT_CLIENT_TIMEOUT:-20} ``` This sets the `TIDB_ON_QDRANT_CLIENT_TIMEOUT` to the value of the environment variable `TIDB_ON_QDRANT_CLIENT_TIMEOUT` if it is set, or defaults to `20` seconds if it is not set. Make sure to update your `docker-compose.yaml` file accordingly. <!-- Dosu Comment Footer --> *To continue talking to [Dosu](https://dosu.dev), mention @dosu.*
yindo commented 2026-02-21 18:15:42 -05:00
Author
Owner
Copy Link
Copy Source

@Eyal51 commented on GitHub (Oct 29, 2024):

@dosu fix the docker-compose.yaml in the repo

@Eyal51 commented on GitHub (Oct 29, 2024): @dosu fix the `docker-compose.yaml` in the repo
yindo commented 2026-02-21 18:15:42 -05:00
Author
Owner
Copy Link
Copy Source

@dosubot[bot] commented on GitHub (Oct 29, 2024):

This issue seems to need your specialized knowledge, @takatost, could you please take a look?

To continue talking to Dosu, mention @dosu.

@dosubot[bot] commented on GitHub (Oct 29, 2024): <!-- Answer --> This issue seems to need your specialized knowledge, @takatost, could you please take a look? <!-- Dosu Comment Footer --> *To continue talking to [Dosu](https://dosu.dev), mention @dosu.*
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
Knowledge Pipeline
Proposal
WIP
cloud
dependencies
feat:webapp
good first issue
outdated
performance
pull-request
Mirrored from GitHub Pull Request
 python:uv
refactor
size:L
stale
status: accepting prs
status: blocked
status: in discussion
stt & tts
vulnerablity
web
wont-fix
🌊 feat:workflow
🌚 invalid
🐞 bug
👻 feat:rag
💪 enhancement
📚 documentation
🔨 feat:tools
🙋‍♂️ question
🙏 help wanted
🤔 cant-reproduce
🤖 feat:agent
No Label 👻 feat:rag
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
yindo
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: langgenius/dify#6427
Delete Branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?