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

Unable to extract the file name #6556

New Issue
Closed
opened 2026-02-21 18:16:17 -05:00 by yindo · 2 comments
yindo commented 2026-02-21 18:16:17 -05:00
Owner
Copy Link
Copy Source

Originally created by @bjev-xie on GitHub (Nov 5, 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

0.10.0

Cloud or Self Hosted

Self Hosted (Docker)

Steps to reproduce

Create a new workflow. Add a single file to the start, and connect the start module to either code execution or a large model. During the code execution or within the large model, attempt to extract the file name using File.name. However, an error indicating failure is prompted.

✔️ Expected Behavior

The file name can be extracted.

❌ Actual Behavior

Unable to extract the file name
error
input

Originally created by @bjev-xie on GitHub (Nov 5, 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 0.10.0 ### Cloud or Self Hosted Self Hosted (Docker) ### Steps to reproduce Create a new workflow. Add a single file to the start, and connect the start module to either code execution or a large model. During the code execution or within the large model, attempt to extract the file name using File.name. However, an error indicating failure is prompted. ### ✔️ Expected Behavior The file name can be extracted. ### ❌ Actual Behavior Unable to extract the file name ![error](https://github.com/user-attachments/assets/c1c62b28-7a93-4f31-849a-9ae0ffd070eb) ![input](https://github.com/user-attachments/assets/afefa0c8-e202-46f8-ba01-14e39e616863)
yindo added the 🐞 bug label 2026-02-21 18:16:17 -05:00
yindo closed this issue 2026-02-21 18:16:17 -05:00
yindo commented 2026-02-21 18:16:18 -05:00
Author
Owner
Copy Link
Copy Source

@dosubot[bot] commented on GitHub (Nov 5, 2024):

I couldn't find any specific known issues related to file name extraction in Dify version 0.10.0. However, there are typical error messages related to file handling that might be relevant to your situation. These include errors like "File variable not found for selector" and "Variable is not an ArrayFileSegment," which indicate issues with file variable handling or type mismatches [1].

To troubleshoot, ensure that the file variable is correctly defined and accessible in your workflow. Verify that the file is being passed correctly between modules and that the variable type matches the expected format for file operations. If the problem persists, reviewing the workflow setup and ensuring all configurations are correct might help resolve the issue.

To continue talking to Dosu, mention @dosu.

@dosubot[bot] commented on GitHub (Nov 5, 2024): <!-- Answer --> I couldn't find any specific known issues related to file name extraction in Dify version 0.10.0. However, there are typical error messages related to file handling that might be relevant to your situation. These include errors like "File variable not found for selector" and "Variable is not an ArrayFileSegment," which indicate issues with file variable handling or type mismatches <sup>[[1]](https://github.com/langgenius/dify/blob/main/api/core/workflow/nodes/document_extractor/node.py)</sup>. To troubleshoot, ensure that the file variable is correctly defined and accessible in your workflow. Verify that the file is being passed correctly between modules and that the variable type matches the expected format for file operations. If the problem persists, reviewing the workflow setup and ensuring all configurations are correct might help resolve the issue. <!-- Dosu Comment Footer --> *To continue talking to [Dosu](https://dosu.dev), mention @dosu.*
yindo commented 2026-02-21 18:16:18 -05:00
Author
Owner
Copy Link
Copy Source

@crazywoola commented on GitHub (Nov 5, 2024):

Please upgrade to latest version, we have several fixes regarding these issues.

@crazywoola commented on GitHub (Nov 5, 2024): Please upgrade to latest version, we have several fixes regarding these issues.
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
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#6556
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?