when use multi file, failed with error "Run failed: sequence item 2: expected str instance, list found"

[zhuqingchao]

Self Checks

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

Dify version

0.10.2

Cloud or Self Hosted

Self Hosted (Source)

Steps to reproduce

DSL: multi_file_error.txt I found that prompt_template_parser.py line 36. when the inputs contains array[file] -> array[string] 。 then it failed at line 40. I don't know if I should type match the array directly to a string here, or convert it elsewhere.

✔️ Expected Behavior

propmt template generate success.

❌ Actual Behavior

failed with error

[majestichou]

sys.files is an array, and its output variable is also an array. It cannot be placed directly in the LLM prompt word. You can add LLM to the iteration by connecting an iterator to the document extractor.

[dosubot[bot]]

The error you're encountering, "Run failed: sequence item 2: expected str instance, list found," suggests that the code is trying to concatenate or process a list as if it were a string. This typically happens when a function expects a string but receives a list instead.

In the context of prompt_template_parser.py, it seems like the issue arises when handling inputs that are arrays of files, which are then expected to be strings. To resolve this, you have a couple of options:

1. Convert the List to a String: If the list of files should be treated as a single string, you can join the list elements into a string. For example, you can use ','.join(your_list) to concatenate the list items into a single string separated by commas.

2. Adjust the Code to Handle Lists: If the logic should handle lists differently, you might need to modify the code to process each item in the list individually, rather than expecting a single string.

Without specific details on the intended behavior, it's hard to recommend the exact change. However, if the input is supposed to be a single string, converting the list to a string as shown above might be the simplest solution. If the input should remain a list, you may need to adjust the logic to handle each element appropriately.

To continue talking to Dosu, mention @dosu.

[zhuqingchao]

sys.files is an array, and its output variable is also an array. It cannot be placed directly in the LLM prompt word. You can add LLM to the iteration by connecting an iterator to the document extractor. got it. so array[string] should not be choosed in the graph editor. maybe need to fix this

[crazywoola]

It seems you open a new https://github.com/langgenius/dify/issues/10004 here, this can be closed right?

[zhuqingchao]

It seems you open a new #10004 here, this can be closed right? @crazywoola I think #10004 is another bug. The current bug refers to the ability to select an array[string] generated by the doc extractor array[file] in the prompt of the LLM node. Another issue is that when the start node changes from a single file to multiple files, the output of the doc extractor is still a string instead of an array[string].

[dosubot[bot]]

Hi, @zhuqingchao. I'm Dosu, and I'm helping the Dify team manage their backlog and am marking this issue as stale.

Issue Summary:

• A bug was reported in Dify version 0.10.2 related to handling multiple files, causing a type mismatch error.
• The issue was identified as sys.files being an array, which should not be directly used in the LLM prompt.
• Majestichou suggested using an iterator, while I recommended converting the list to a string or adjusting the code.
• You acknowledged the advice and clarified the issue's distinction from another bug, emphasizing array handling in the graph editor.

Next Steps:

• Please confirm if this issue is still relevant to the latest version of the Dify repository. If so, you can keep the discussion open by commenting on the issue.
• Otherwise, the issue will be automatically closed in 15 days.

Thank you for your understanding and contribution!