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

Exception when using the time tool #8918

New Issue
Closed
opened 2026-02-21 18:28:37 -05:00 by yindo · 10 comments
yindo commented 2026-02-21 18:28:37 -05:00
Owner
Copy Link
Copy Source

Originally created by @accat7080 on GitHub (Mar 3, 2025).

Originally assigned to: @crazywoola on GitHub.

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

0.15.3

Cloud or Self Hosted

Self Hosted (Docker)

Steps to reproduce

My Connfig

app:
description: ''
icon: 🤖
icon_background: '#FFEAD5'
mode: agent-chat
name: Agent-Test
use_icon_as_answer_icon: false
kind: app
model_config:
agent_mode:
enabled: true
max_iteration: 5
prompt: null
strategy: react
tools:
- enabled: true
provider_id: time
provider_name: time
provider_type: builtin
tool_label: 获取当前时间
tool_name: current_time
tool_parameters:
format: ''
timezone: ''
- enabled: true
provider_id: time
provider_name: time
provider_type: builtin
tool_label: 时间戳转换
tool_name: timestamp_to_localtime
tool_parameters:
timestamp: ''
timezone: ''
- enabled: true
provider_id: time
provider_name: time
provider_type: builtin
tool_label: 星期几计算器
tool_name: weekday
tool_parameters:
day: ''
month: ''
year: ''
- enabled: true
provider_id: time
provider_name: time
provider_type: builtin
tool_label: 时区转换
tool_name: timezone_conversion
tool_parameters:
current_time: ''
current_timezone: ''
target_timezone: ''
- enabled: true
provider_id: time
provider_name: time
provider_type: builtin
tool_label: 获取时间戳
tool_name: localtime_to_timestamp
tool_parameters:
localtime: ''
timezone: ''
annotation_reply:
enabled: false
chat_prompt_config: {}
completion_prompt_config: {}
dataset_configs:
datasets:
datasets: []
reranking_enable: false
retrieval_model: multiple
top_k: 4
dataset_query_variable: ''
external_data_tools: []
file_upload:
allowed_file_extensions:
- .JPG
- .JPEG
- .PNG
- .GIF
- .WEBP
- .SVG
- .MP4
- .MOV
- .MPEG
- .MPGA
allowed_file_types: []
allowed_file_upload_methods:
- remote_url
- local_file
enabled: false
image:
detail: high
enabled: false
number_limits: 3
transfer_methods:
- remote_url
- local_file
number_limits: 3
model:
completion_params:
stop: []
mode: chat
name: deepseek-r1:14b
provider: ollama
more_like_this:
enabled: false
opening_statement: ''
pre_prompt: ''
prompt_type: simple
retriever_resource:
enabled: true
sensitive_word_avoidance:
configs: []
enabled: false
type: ''
speech_to_text:
enabled: false
suggested_questions: []
suggested_questions_after_answer:
enabled: false
text_to_speech:
enabled: false
language: ''
voice: ''
user_input_form: []
version: 0.1.5

When I create an Agent using this configuration and ask "Please answer what date is it today?", it doesn't respond at all.

To find out today's date, I'll use the current_time tool.

{
"action": "current_time"
}

Image

✔️ Expected Behavior

No response

❌ Actual Behavior

No response

Originally created by @accat7080 on GitHub (Mar 3, 2025). Originally assigned to: @crazywoola on GitHub. ### 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 0.15.3 ### Cloud or Self Hosted Self Hosted (Docker) ### Steps to reproduce # My Connfig app: description: '' icon: 🤖 icon_background: '#FFEAD5' mode: agent-chat name: Agent-Test use_icon_as_answer_icon: false kind: app model_config: agent_mode: enabled: true max_iteration: 5 prompt: null strategy: react tools: - enabled: true provider_id: time provider_name: time provider_type: builtin tool_label: 获取当前时间 tool_name: current_time tool_parameters: format: '' timezone: '' - enabled: true provider_id: time provider_name: time provider_type: builtin tool_label: 时间戳转换 tool_name: timestamp_to_localtime tool_parameters: timestamp: '' timezone: '' - enabled: true provider_id: time provider_name: time provider_type: builtin tool_label: 星期几计算器 tool_name: weekday tool_parameters: day: '' month: '' year: '' - enabled: true provider_id: time provider_name: time provider_type: builtin tool_label: 时区转换 tool_name: timezone_conversion tool_parameters: current_time: '' current_timezone: '' target_timezone: '' - enabled: true provider_id: time provider_name: time provider_type: builtin tool_label: 获取时间戳 tool_name: localtime_to_timestamp tool_parameters: localtime: '' timezone: '' annotation_reply: enabled: false chat_prompt_config: {} completion_prompt_config: {} dataset_configs: datasets: datasets: [] reranking_enable: false retrieval_model: multiple top_k: 4 dataset_query_variable: '' external_data_tools: [] file_upload: allowed_file_extensions: - .JPG - .JPEG - .PNG - .GIF - .WEBP - .SVG - .MP4 - .MOV - .MPEG - .MPGA allowed_file_types: [] allowed_file_upload_methods: - remote_url - local_file enabled: false image: detail: high enabled: false number_limits: 3 transfer_methods: - remote_url - local_file number_limits: 3 model: completion_params: stop: [] mode: chat name: deepseek-r1:14b provider: ollama more_like_this: enabled: false opening_statement: '' pre_prompt: '' prompt_type: simple retriever_resource: enabled: true sensitive_word_avoidance: configs: [] enabled: false type: '' speech_to_text: enabled: false suggested_questions: [] suggested_questions_after_answer: enabled: false text_to_speech: enabled: false language: '' voice: '' user_input_form: [] version: 0.1.5 When I create an Agent using this configuration and ask "Please answer what date is it today?", it doesn't respond at all. To find out today's date, I'll use the current_time tool. { "action": "current_time" } ![Image](https://github.com/user-attachments/assets/00bf9a9e-424f-498e-b6d0-1b2eec0c50b6) ### ✔️ Expected Behavior _No response_ ### ❌ Actual Behavior _No response_
yindo added the 🐞 bug🔨 feat:tools labels 2026-02-21 18:28:37 -05:00
yindo closed this issue 2026-02-21 18:28:37 -05:00
yindo commented 2026-02-21 18:28:38 -05:00
Author
Owner
Copy Link
Copy Source

@dosubot[bot] commented on GitHub (Mar 3, 2025):

Hello, @accat7080! I'm here to help you with any bugs, questions, or contributions you have. Let's get your issue sorted out!

The issue you're experiencing with the 'current_time' tool not responding could be related to the tool parameters being incorrectly set or missing. In your configuration, the format and timezone parameters for the 'current_time' tool are empty. The 'current_time' tool in Dify has default parameters, where the format should be "%Y-%m-%d %H:%M:%S" and the timezone should be "UTC" if not specified [1].

To resolve this, try setting the format and timezone parameters explicitly in your configuration. For example:

tool_parameters:
  format: "%Y-%m-%d %H:%M:%S"
  timezone: "UTC"

This should help the tool execute correctly and provide the current date and time as expected. If the issue persists, ensure that there are no other configuration errors or missing dependencies that might affect the tool's execution.

To continue talking to Dosu, mention @dosu.

Help Dosu learn! Give it feedback: Great Response | Irrelevant Answer | Incorrect Sources | Too Verbose | Hallucination | Bug Report | Other

@dosubot[bot] commented on GitHub (Mar 3, 2025): <!-- Greeting --> Hello, @accat7080! I'm here to help you with any bugs, questions, or contributions you have. Let's get your issue sorted out! <!-- Answer --> The issue you're experiencing with the 'current_time' tool not responding could be related to the tool parameters being incorrectly set or missing. In your configuration, the `format` and `timezone` parameters for the 'current_time' tool are empty. The 'current_time' tool in Dify has default parameters, where the `format` should be "%Y-%m-%d %H:%M:%S" and the `timezone` should be "UTC" if not specified <sup>[[1]](https://github.com/langgenius/dify/blob/main/api/core/tools/builtin_tool/providers/time/tools/current_time.yaml)</sup>. To resolve this, try setting the `format` and `timezone` parameters explicitly in your configuration. For example: ```yaml tool_parameters: format: "%Y-%m-%d %H:%M:%S" timezone: "UTC" ``` This should help the tool execute correctly and provide the current date and time as expected. If the issue persists, ensure that there are no other configuration errors or missing dependencies that might affect the tool's execution. <!-- Dosu Comment Footer --> *To continue talking to [Dosu](https://dosu.dev), mention @dosu.* --- <sup>Help Dosu learn! Give it feedback: [Great Response](https://app.dosu.dev/response-feedback/0448ad7e-1805-4582-9e94-f940d171a6be?feedback_type=great_response) | [Irrelevant Answer](https://app.dosu.dev/response-feedback/0448ad7e-1805-4582-9e94-f940d171a6be?feedback_type=irrelevant_answer) | [Incorrect Sources](https://app.dosu.dev/response-feedback/0448ad7e-1805-4582-9e94-f940d171a6be?feedback_type=incorrect_sources) | [Too Verbose](https://app.dosu.dev/response-feedback/0448ad7e-1805-4582-9e94-f940d171a6be?feedback_type=too_verbose) | [Hallucination](https://app.dosu.dev/response-feedback/0448ad7e-1805-4582-9e94-f940d171a6be?feedback_type=hallucination) | [Bug Report](https://app.dosu.dev/response-feedback/0448ad7e-1805-4582-9e94-f940d171a6be?feedback_type=bug_report) | [Other](https://app.dosu.dev/response-feedback/0448ad7e-1805-4582-9e94-f940d171a6be?feedback_type=other)</sup>
yindo commented 2026-02-21 18:28:38 -05:00
Author
Owner
Copy Link
Copy Source

@accat7080 commented on GitHub (Mar 3, 2025):

Image

Image

Image

I have already configured the time zone and format, but the returned content is still incorrect.

@accat7080 commented on GitHub (Mar 3, 2025): ![Image](https://github.com/user-attachments/assets/f392e551-a207-4db0-bea7-43cc5e7a1c05) ![Image](https://github.com/user-attachments/assets/81744eb0-2703-4cac-b484-4d4c53f27250) ![Image](https://github.com/user-attachments/assets/5053d33c-04f0-4346-8bcb-aa078b777775) I have already configured the time zone and format, but the returned content is still incorrect.
yindo commented 2026-02-21 18:28:38 -05:00
Author
Owner
Copy Link
Copy Source

@accat7080 commented on GitHub (Mar 3, 2025):

@dosu I didn't observe any error messages when using the command "docker compose logs -f" either.

@accat7080 commented on GitHub (Mar 3, 2025): @dosu I didn't observe any error messages when using the command "docker compose logs -f" either.
yindo commented 2026-02-21 18:28:38 -05:00
Author
Owner
Copy Link
Copy Source

@dosubot[bot] commented on GitHub (Mar 3, 2025):

If you've configured the timezone and format correctly but the "current_time" tool is still returning incorrect content, there are a few things to check:

  1. Timezone Validity: Ensure that the timezone string you are using is valid. The "current_time" tool recognizes specific timezone strings such as "Asia/Shanghai" [1].

  2. Daylight Saving Time: If the timezone is valid, verify that the timezone object is correctly handling daylight saving time or other timezone-specific adjustments. This can sometimes cause discrepancies if not properly configured [2].

  3. System Timezone Database: Check if the system's timezone database is up to date. An outdated database can affect timezone calculations and lead to incorrect time being returned [2].

  4. Default Behavior: If the timezone is not specified or is invalid, the tool defaults to "UTC". Make sure the timezone is correctly specified to avoid this default behavior [2].

If all these aspects are correctly configured and the issue persists, further investigation into the environment's settings might be necessary.

To continue talking to Dosu, mention @dosu.

Help Dosu learn! Give it feedback: Great Response | Irrelevant Answer | Incorrect Sources | Too Verbose | Hallucination | Bug Report | Other

@dosubot[bot] commented on GitHub (Mar 3, 2025): <!-- Answer --> If you've configured the timezone and format correctly but the "current_time" tool is still returning incorrect content, there are a few things to check: 1. **Timezone Validity**: Ensure that the timezone string you are using is valid. The "current_time" tool recognizes specific timezone strings such as "Asia/Shanghai" <sup>[[1]](https://github.com/langgenius/dify/blob/main/api/core/tools/builtin_tool/providers/time/tools/current_time.yaml)</sup>. 2. **Daylight Saving Time**: If the timezone is valid, verify that the timezone object is correctly handling daylight saving time or other timezone-specific adjustments. This can sometimes cause discrepancies if not properly configured <sup>[[2]](https://github.com/langgenius/dify/blob/main/api/core/tools/provider/builtin/time/tools/current_time.py)</sup>. 3. **System Timezone Database**: Check if the system's timezone database is up to date. An outdated database can affect timezone calculations and lead to incorrect time being returned <sup>[[2]](https://github.com/langgenius/dify/blob/main/api/core/tools/provider/builtin/time/tools/current_time.py)</sup>. 4. **Default Behavior**: If the timezone is not specified or is invalid, the tool defaults to "UTC". Make sure the timezone is correctly specified to avoid this default behavior <sup>[[2]](https://github.com/langgenius/dify/blob/main/api/core/tools/provider/builtin/time/tools/current_time.py)</sup>. If all these aspects are correctly configured and the issue persists, further investigation into the environment's settings might be necessary. <!-- Dosu Comment Footer --> *To continue talking to [Dosu](https://dosu.dev), mention @dosu.* --- <sup>Help Dosu learn! Give it feedback: [Great Response](https://app.dosu.dev/response-feedback/a5a94a0a-4dc4-4515-a63b-0a049caf265d?feedback_type=great_response) | [Irrelevant Answer](https://app.dosu.dev/response-feedback/a5a94a0a-4dc4-4515-a63b-0a049caf265d?feedback_type=irrelevant_answer) | [Incorrect Sources](https://app.dosu.dev/response-feedback/a5a94a0a-4dc4-4515-a63b-0a049caf265d?feedback_type=incorrect_sources) | [Too Verbose](https://app.dosu.dev/response-feedback/a5a94a0a-4dc4-4515-a63b-0a049caf265d?feedback_type=too_verbose) | [Hallucination](https://app.dosu.dev/response-feedback/a5a94a0a-4dc4-4515-a63b-0a049caf265d?feedback_type=hallucination) | [Bug Report](https://app.dosu.dev/response-feedback/a5a94a0a-4dc4-4515-a63b-0a049caf265d?feedback_type=bug_report) | [Other](https://app.dosu.dev/response-feedback/a5a94a0a-4dc4-4515-a63b-0a049caf265d?feedback_type=other)</sup>
yindo commented 2026-02-21 18:28:38 -05:00
Author
Owner
Copy Link
Copy Source

@accat7080 commented on GitHub (Mar 3, 2025):

URL: https://ai.gongwuyun.com/console/api/apps/91a92428-9354-4e7c-a5f9-2b717fd73ec0/chat-messages
Method: POST
@dosu
Image

@accat7080 commented on GitHub (Mar 3, 2025): URL: https://ai.gongwuyun.com/console/api/apps/91a92428-9354-4e7c-a5f9-2b717fd73ec0/chat-messages Method: POST @dosu ![Image](https://github.com/user-attachments/assets/04f1e694-1092-4338-a75d-714611a58c2f)
yindo commented 2026-02-21 18:28:38 -05:00
Author
Owner
Copy Link
Copy Source

@dosubot[bot] commented on GitHub (Mar 3, 2025):

To ensure the "current_time" tool returns the correct date and time when using the "chat-messages" API with the Asia/Shanghai timezone, make sure the timezone parameter is set to "Asia/Shanghai" in the tool_parameters dictionary. Here's an example configuration:

{
  "tool_parameters": {
    "timezone": "Asia/Shanghai",
    "format": "%Y-%m-%d %H:%M:%S"
  }
}

This configuration should be included in your API request to ensure the time is correctly interpreted and returned in the Asia/Shanghai timezone. If the issue persists, verify that the timezone string is valid and that your system's timezone database is up to date to avoid discrepancies [1].

To continue talking to Dosu, mention @dosu.

Help Dosu learn! Give it feedback: Great Response | Irrelevant Answer | Incorrect Sources | Too Verbose | Hallucination | Bug Report | Other

@dosubot[bot] commented on GitHub (Mar 3, 2025): <!-- Answer --> To ensure the "current_time" tool returns the correct date and time when using the "chat-messages" API with the Asia/Shanghai timezone, make sure the `timezone` parameter is set to "Asia/Shanghai" in the `tool_parameters` dictionary. Here's an example configuration: ```json { "tool_parameters": { "timezone": "Asia/Shanghai", "format": "%Y-%m-%d %H:%M:%S" } } ``` This configuration should be included in your API request to ensure the time is correctly interpreted and returned in the Asia/Shanghai timezone. If the issue persists, verify that the timezone string is valid and that your system's timezone database is up to date to avoid discrepancies <sup>[[1]](https://github.com/langgenius/dify/blob/main/api/core/tools/builtin_tool/providers/time/tools/current_time.py)</sup>. <!-- Dosu Comment Footer --> *To continue talking to [Dosu](https://dosu.dev), mention @dosu.* --- <sup>Help Dosu learn! Give it feedback: [Great Response](https://app.dosu.dev/response-feedback/c29fb2ce-2f3c-455e-a715-f7cd6b483720?feedback_type=great_response) | [Irrelevant Answer](https://app.dosu.dev/response-feedback/c29fb2ce-2f3c-455e-a715-f7cd6b483720?feedback_type=irrelevant_answer) | [Incorrect Sources](https://app.dosu.dev/response-feedback/c29fb2ce-2f3c-455e-a715-f7cd6b483720?feedback_type=incorrect_sources) | [Too Verbose](https://app.dosu.dev/response-feedback/c29fb2ce-2f3c-455e-a715-f7cd6b483720?feedback_type=too_verbose) | [Hallucination](https://app.dosu.dev/response-feedback/c29fb2ce-2f3c-455e-a715-f7cd6b483720?feedback_type=hallucination) | [Bug Report](https://app.dosu.dev/response-feedback/c29fb2ce-2f3c-455e-a715-f7cd6b483720?feedback_type=bug_report) | [Other](https://app.dosu.dev/response-feedback/c29fb2ce-2f3c-455e-a715-f7cd6b483720?feedback_type=other)</sup>
yindo commented 2026-02-21 18:28:38 -05:00
Author
Owner
Copy Link
Copy Source

@crazywoola commented on GitHub (Mar 3, 2025):

Duplicated https://github.com/langgenius/dify/issues/14760

@crazywoola commented on GitHub (Mar 3, 2025): Duplicated https://github.com/langgenius/dify/issues/14760
yindo commented 2026-02-21 18:28:38 -05:00
Author
Owner
Copy Link
Copy Source

@accat7080 commented on GitHub (Mar 3, 2025):

Image

Image

After installing the dependencies in the containers docker-worker-1, docker-api-1, and docker-sandbox-1 according to the file https://github.com/langgenius/dify/blob/0.15.3/api/core/tools/provider/builtin/time/tools/current_time.py using the commands pip3 install pytz -i https://mirrors.aliyun.com/pypi/simple/, pip3 install datetime -i https://mirrors.aliyun.com/pypi/simple/, and pip3 install typing -i https://mirrors.aliyun.com/pypi/simple/, and restarting the services with cd /data/dify/docker; docker compose restart, I encountered an error when accessing it again.

tool_parameters should be a dict, but got a string:

@crazywoola @dosu

@accat7080 commented on GitHub (Mar 3, 2025): ![Image](https://github.com/user-attachments/assets/2e5b65e5-447a-42b6-ac5a-c8df5146a84b) ![Image](https://github.com/user-attachments/assets/beeca126-f1d9-48ee-8df6-1a80d7a80b2a) After installing the dependencies in the containers docker-worker-1, docker-api-1, and docker-sandbox-1 according to the file https://github.com/langgenius/dify/blob/0.15.3/api/core/tools/provider/builtin/time/tools/current_time.py using the commands pip3 install pytz -i https://mirrors.aliyun.com/pypi/simple/, pip3 install datetime -i https://mirrors.aliyun.com/pypi/simple/, and pip3 install typing -i https://mirrors.aliyun.com/pypi/simple/, and restarting the services with cd /data/dify/docker; docker compose restart, I encountered an error when accessing it again. tool_parameters should be a dict, but got a string: @crazywoola @dosu
yindo commented 2026-02-21 18:28:39 -05:00
Author
Owner
Copy Link
Copy Source

@dosubot[bot] commented on GitHub (Mar 3, 2025):

The error "tool_parameters should be a dict, but got a string" suggests that the tool_parameters for the current_time tool are not being passed correctly. Ensure that you are passing tool_parameters as a dictionary, not a string. Here's how you can structure it:

tool_parameters = {
    "format": "%Y-%m-%d %H:%M:%S",  # Optional, default is "%Y-%m-%d %H:%M:%S"
    "timezone": "Asia/Shanghai"  # Optional, default is "UTC"
}

If you are using a JSON string, make sure it is correctly formatted and can be parsed into a dictionary. For example:

tool_parameters = '{"format": "%Y-%m-%d %H:%M:%S", "timezone": "Asia/Shanghai"}'

Ensure that this JSON string is properly converted to a dictionary before being used. If the conversion fails, it will raise the error you encountered. Make sure to check your code to ensure that tool_parameters is indeed a dictionary when passed to the current_time tool [1][2].

I didn't find any similar threads related to this specific issue, so it seems unique to your current setup. If you continue to experience issues, double-check the formatting and ensure all dependencies are correctly installed and up to date.

To continue talking to Dosu, mention @dosu.

Help Dosu learn! Give it feedback: Great Response | Irrelevant Answer | Incorrect Sources | Too Verbose | Hallucination | Bug Report | Other

@dosubot[bot] commented on GitHub (Mar 3, 2025): <!-- Answer --> The error "tool_parameters should be a dict, but got a string" suggests that the `tool_parameters` for the `current_time` tool are not being passed correctly. Ensure that you are passing `tool_parameters` as a dictionary, not a string. Here's how you can structure it: ```python tool_parameters = { "format": "%Y-%m-%d %H:%M:%S", # Optional, default is "%Y-%m-%d %H:%M:%S" "timezone": "Asia/Shanghai" # Optional, default is "UTC" } ``` If you are using a JSON string, make sure it is correctly formatted and can be parsed into a dictionary. For example: ```python tool_parameters = '{"format": "%Y-%m-%d %H:%M:%S", "timezone": "Asia/Shanghai"}' ``` Ensure that this JSON string is properly converted to a dictionary before being used. If the conversion fails, it will raise the error you encountered. Make sure to check your code to ensure that `tool_parameters` is indeed a dictionary when passed to the `current_time` tool <sup>[[1]](https://github.com/langgenius/dify/blob/main/api/core/tools/tool_engine.py)</sup><sup>[[2]](https://github.com/langgenius/dify/blob/main/api/core/tools/builtin_tool/providers/time/tools/current_time.yaml)</sup>. I didn't find any similar threads related to this specific issue, so it seems unique to your current setup. If you continue to experience issues, double-check the formatting and ensure all dependencies are correctly installed and up to date. <!-- Dosu Comment Footer --> *To continue talking to [Dosu](https://dosu.dev), mention @dosu.* --- <sup>Help Dosu learn! Give it feedback: [Great Response](https://app.dosu.dev/response-feedback/c2e3cc67-5471-4d7c-84b0-96b42b7073f1?feedback_type=great_response) | [Irrelevant Answer](https://app.dosu.dev/response-feedback/c2e3cc67-5471-4d7c-84b0-96b42b7073f1?feedback_type=irrelevant_answer) | [Incorrect Sources](https://app.dosu.dev/response-feedback/c2e3cc67-5471-4d7c-84b0-96b42b7073f1?feedback_type=incorrect_sources) | [Too Verbose](https://app.dosu.dev/response-feedback/c2e3cc67-5471-4d7c-84b0-96b42b7073f1?feedback_type=too_verbose) | [Hallucination](https://app.dosu.dev/response-feedback/c2e3cc67-5471-4d7c-84b0-96b42b7073f1?feedback_type=hallucination) | [Bug Report](https://app.dosu.dev/response-feedback/c2e3cc67-5471-4d7c-84b0-96b42b7073f1?feedback_type=bug_report) | [Other](https://app.dosu.dev/response-feedback/c2e3cc67-5471-4d7c-84b0-96b42b7073f1?feedback_type=other)</sup>
yindo commented 2026-02-21 18:28:39 -05:00
Author
Owner
Copy Link
Copy Source

@accat7080 commented on GitHub (Mar 3, 2025):

I'm really confused because after I cloned the code, I directly used docker compose up -d to start it, and all the configurations were default. Did I miss making some changes?
@dosu

@accat7080 commented on GitHub (Mar 3, 2025): I'm really confused because after I cloned the code, I directly used docker compose up -d to start it, and all the configurations were default. Did I miss making some changes? @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 🐞 bug 🔨 feat:tools
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#8918
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?