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

After upgrading to version 1.4.0, the files returned by the plugin cannot display their original file names properly. #13982

New Issue
Closed
opened 2026-02-21 19:14:54 -05:00 by yindo · 2 comments
yindo commented 2026-02-21 19:14:54 -05:00
Owner
Copy Link
Copy Source

Originally created by @lfenghx on GitHub (May 18, 2025).

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.4.0

Cloud or Self Hosted

Self Hosted (Docker)

Steps to reproduce

I download and return files through a plugin. In version 1.3, the name decoding worked normally, and the original file names could be displayed. However, after upgrading to version 1.4.0, this no longer works. The file names returned by the plugin are all UUIDs instead of the original file names!

✔️ Expected Behavior

I hope that the plugin can return the original file names normally, just like in version 1.3.

❌ Actual Behavior

The file names have become long strings of characters, similar to UUIDs.

Originally created by @lfenghx on GitHub (May 18, 2025). ### 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.4.0 ### Cloud or Self Hosted Self Hosted (Docker) ### Steps to reproduce I download and return files through a plugin. In version 1.3, the name decoding worked normally, and the original file names could be displayed. However, after upgrading to version 1.4.0, this no longer works. The file names returned by the plugin are all UUIDs instead of the original file names! ### ✔️ Expected Behavior I hope that the plugin can return the original file names normally, just like in version 1.3. ### ❌ Actual Behavior The file names have become long strings of characters, similar to UUIDs.
yindo added the 🐞 bug label 2026-02-21 19:14:54 -05:00
yindo closed this issue 2026-02-21 19:14:55 -05:00
yindo commented 2026-02-21 19:14:55 -05:00
Author
Owner
Copy Link
Copy Source

@dosubot[bot] commented on GitHub (May 18, 2025):

It seems like there might be a change in how file names are handled by the plugin in version 1.4.0. Unfortunately, I couldn't find specific information about changes related to file name handling between versions 1.3 and 1.4.0 in the repository or documentation.

However, you might want to check if there are any new configurations or settings introduced in version 1.4.0 that could affect file name processing. Additionally, reviewing the changelog or release notes for version 1.4.0 might provide insights into any modifications that could be causing this issue. If the problem persists, consider checking the plugin's code for any changes in file name encoding or decoding logic.

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 (May 18, 2025): <!-- Answer --> It seems like there might be a change in how file names are handled by the plugin in version 1.4.0. Unfortunately, I couldn't find specific information about changes related to file name handling between versions 1.3 and 1.4.0 in the repository or documentation. However, you might want to check if there are any new configurations or settings introduced in version 1.4.0 that could affect file name processing. Additionally, reviewing the changelog or release notes for version 1.4.0 might provide insights into any modifications that could be causing this issue. If the problem persists, consider checking the plugin's code for any changes in file name encoding or decoding logic. <!-- 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/91ef1580-d46f-45d0-8904-36f704a8ae15?feedback_type=great_response) | [Irrelevant Answer](https://app.dosu.dev/response-feedback/91ef1580-d46f-45d0-8904-36f704a8ae15?feedback_type=irrelevant_answer) | [Incorrect Sources](https://app.dosu.dev/response-feedback/91ef1580-d46f-45d0-8904-36f704a8ae15?feedback_type=incorrect_sources) | [Too Verbose](https://app.dosu.dev/response-feedback/91ef1580-d46f-45d0-8904-36f704a8ae15?feedback_type=too_verbose) | [Hallucination](https://app.dosu.dev/response-feedback/91ef1580-d46f-45d0-8904-36f704a8ae15?feedback_type=hallucination) | [Bug Report](https://app.dosu.dev/response-feedback/91ef1580-d46f-45d0-8904-36f704a8ae15?feedback_type=bug_report) | [Other](https://app.dosu.dev/response-feedback/91ef1580-d46f-45d0-8904-36f704a8ae15?feedback_type=other)</sup>
yindo commented 2026-02-21 19:14:55 -05:00
Author
Owner
Copy Link
Copy Source

@lfenghx commented on GitHub (May 18, 2025):

The issue has been resolved. It's because, compared with version 1.3, version 1.4 of Dify has strengthened the metadata specification for create_blob_message. The file name should be specified using "filename" instead of "file_name".

@lfenghx commented on GitHub (May 18, 2025): The issue has been resolved. It's because, compared with version 1.3, version 1.4 of Dify has strengthened the metadata specification for create_blob_message. The file name should be specified using "filename" instead of "file_name".
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#13982
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?