mirror of
https://github.com/langgenius/dify-official-plugins.git
synced 2026-07-21 17:45:23 -04:00
MinerU 0.5.1 Run multiple files bug. #828
Reference in New Issue
Block a user
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?
Originally created by @suntao2015005848 on GitHub (Nov 24, 2025).
Self Checks
Dify version
1.9.1
Cloud or Self Hosted
Self Hosted (Docker)
Steps to reproduce
Please resolve the multi-file upload parsing issue in the MinerU Dify Plugin version 0.5.1.
✔️ Expected Behavior
❌ Actual Behavior
No response
@dosubot[bot] commented on GitHub (Nov 24, 2025):
The MinerU plugin v0.5.1 only supports single-file input—both the tool schema and backend code expect a single file, not an array. If you provide multiple files, only the first is processed and the rest are ignored, which causes the workflow to fail when a step expects a single file but receives multiple files instead. This is a known limitation and is tracked in open issues, but there is no official fix or merged pull request for multi-file support yet.
If you need multi-file upload support now, the best-practice workaround is to customize the OpenAPI schema for the plugin: define the
filesparameter as an array of binary strings and add aserverselement. This allows you to transfer multiple files into the Dify app and process them as needed. You can see an example of this workaround and schema in this discussion.To fully support multi-file uploads, both the plugin's YAML schema and the backend code would need to be updated to accept and process arrays of files instead of a single file parameter.
To reply, just mention @dosu.
How did I do? Good | Irrelevant | Incorrect | Verbose | Hallucination | Report 🐛 | Other
@dosubot[bot] commented on GitHub (Nov 25, 2025):
The MinerU plugin v0.5.1 only supports single file uploads—both the local and remote parsing logic expect a single file object and do not handle lists of files. When multiple files are uploaded, the plugin processes only the first file and ignores the rest, which causes the workflow to fail if the parameter receives more than one file. This is a limitation in the plugin code, even though the backend API supports arrays of files in its schema. There is no official fix for this as of now. A user workaround is to customize the OpenAPI schema and implement a custom tool to handle multi-file uploads, but this requires manual changes and is not part of the official plugin release. If you need to process multiple files, you can upload them one at a time or consider adapting the plugin code to iterate over a list of files and submit each to the backend in sequence. For more details, see the code and related discussion here and here.
To reply, just mention @dosu.
How did I do? Good | Irrelevant | Incorrect | Verbose | Hallucination | Report 🐛 | Other