langgenius / dify

Dify is an open-source LLM app development platform. Dify's intuitive interface combines AI workflow, RAG pipeline, agent capabilities, model management, observability features and more, letting you quickly go from prototype to production.
https://dify.ai
Other
45.3k stars 6.36k forks source link

Error is displayed in selecting the tool for the node. #7518

Closed asemandeveloper closed 1 week ago

asemandeveloper commented 3 weeks ago

Self Checks

Dify version

0.7.1

Cloud or Self Hosted

Self Hosted (Source)

Steps to reproduce

When I run DIFY as Local Source Code. In the workflow, when selecting the tool for the node an error is displayed in selecting the tool for the node. See the pictures below.

image

image

✔️ Expected Behavior

No response

❌ Actual Behavior

No response

dosubot[bot] commented 3 weeks ago

The error displayed when selecting the tool for the node in Dify version 0.7.1, self-hosted, is likely due to the Node.js version requirement. According to the package.json file, Dify version 0.7.1 requires Node.js version >=18.17.0. If the Node.js version installed on your system does not meet this requirement, it could cause errors.

"engines": {
  "node": ">=18.17.0"
}

Ensure that your Node.js version is 18.17.0 or higher to avoid such errors [1].

Additionally, the error might be related to the tool's authorization or configuration. Before using built-in tools, you may need to authorize them. If the built-in tools do not meet your requirements, you can create custom tools within the Dify menu navigation under "Tools." The setup of tool nodes generally involves two steps:

  1. Authorizing the tool/creating a custom tool/publishing a workflow as a tool.
  2. Setting the tool input and parameters.

For more detailed instructions on creating and configuring tools, refer to the tool setup documentation [2].

To continue talking to Dosu, mention @dosu.

asemandeveloper commented 3 weeks ago

The installed node.js version is 18.17.0

crazywoola commented 3 weeks ago

Can't reproduce this problem in latest main branch.

image

We recommend using node version >= v21.

asemandeveloper commented 3 weeks ago

Unfortunately, the problem was not solved!

crazywoola commented 3 weeks ago

But I can not reproduce this either. Is there any errors in console?

asemandeveloper commented 3 weeks ago

But I can not reproduce this either. Is there any errors in console?

This is the last message I receive on the console!

image

crazywoola commented 3 weeks ago

Any errors in frontend console?