mirror of
https://github.com/langgenius/dify-official-plugins.git
synced 2026-07-21 17:45:23 -04:00
Issue with MinerU plugin where files and images always remain empty #744
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 @tomy-kyu on GitHub (Oct 22, 2025).
Self Checks
Dify version
1.8.1
Plugin version
langgenius / mineru 0.5.0
Cloud or Self Hosted
Self Hosted (Docker)
Steps to reproduce
I am using the MinerU plugin to analyze PDF documents, crop images, and retrieve the resulting files.
I have chosen the "pipeline" execution mode due to its accuracy, with processing being performed on GPU hardware.
I'm using the mineru-api container for this operation.
While running with MinerU plugin version 0.5.0, the images aren't being stored in either the "files" or "images" directories, and the list always remains empty.
Previously, with MinerU plugin version 0.2.0 + Mineru-API:1.23, I was successfully able to retrieve images. I'd like to resolve this issue where the image retrieval functionality has stopped working.
✔️ Error log
mineru Container logs
MinerU Plugin executed output
Due to security reasons, many parts had to be omitted, and we sincerely apologize for this.When checking the actual output, there are about eight images—this is supposed to be listed either in
filesorimages. However, what used to work previously now consistently returns an empty result.@dosubot[bot] commented on GitHub (Nov 8, 2025):
Hi, @tomy-kyu. I'm Dosu, and I'm helping the dify-official-plugins team manage their backlog and am marking this issue as stale.
Issue Summary:
Next Steps:
Thank you for your understanding and contribution!
@tomy-kyu commented on GitHub (Nov 11, 2025):
No, I applied version 0.5.1, but the issue remains unresolved. For the time being, we've implemented a workaround by customizing and deploying OpenAPI.json, which while requiring some effort, has enabled the desired functionality—so there's no immediate urgency.
As a workaround, we successfully implemented a custom tool using the JSON text with the added "servers" element, allowing us to successfully transfer file data into the Dify app. Below is a reference to this implementation for reference:
@tomy-kyu commented on GitHub (Nov 11, 2025):
Note that downloaded image data arrives encoded in base64 format. To treat this data as a file object, you'll need to implement additional mechanisms—either by uploading it to Dify or by implementing base64 decoding functionality—so please keep this in mind.
@dosubot[bot] commented on GitHub (Nov 11, 2025):
@crazywoola The user tomy-kyu reports that the issue persists in version 0.5.1 but has implemented a workaround by customizing and deploying OpenAPI.json with a "servers" element to transfer file data successfully. Could you please assist with this?