mirror of
https://github.com/langgenius/dify-official-plugins.git
synced 2026-07-21 17:45:23 -04:00
MinerU plugin encountered an error in extracting doc and docx files #241
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 @moncat2005 on GitHub (Apr 30, 2025).
Self Checks
Dify version
1.2.0
Plugin version
minerU 0.2.0
Cloud or Self Hosted
Self Hosted (Docker)
Steps to reproduce
The miner U plugin itself displays the ability to extract doc or docx documents.
1.when extracting the docx file, an error was found: "Failed to parse file. result: f " error \ ": " Error locating Libreoffice: Libreoffice not found.
My testing environment is Docker Desktop under WIN11.
Dify and Mineru API are both deployed using Docker,
How should the required liberoffice be installed so that it can be correctly called by plugins?
2.An error was found while extracting the doc file: Detected file type does not match thespecified type. Please verify the file.
✔️ Error log
@hjlarry commented on GitHub (May 5, 2025):
this works for me
@moncat2005 commented on GitHub (May 6, 2025):
@hjlarry Thank you！
I tried installing libreoffice inside the container
Testing docx file extraction no longer reports error messages for missing libreoffice
However, an error still occurs when extracting the doc file:
Detected file type does not match thespecified type. Please verify the file.This is the same error message as the default file extractor node when processing DOC files
It seems that the Mineru plugin uses LibreOffice to extract and process docx.
When processing doc files, the same processing method as the default file extractor is used, which prompts for file format errors.
I don't know if the description of the support for extracting document formats in Mineru's plugin is incorrect.
In actual workflow, should we optimize the branch flow of file format judgment conditions
@hjlarry commented on GitHub (May 6, 2025):
The DOC file works fine for me.
The file extractor node uses the
docxlibrary to process DOCX files and leverages the unstructured API to handle DOC files. It seems unrelated toLibreOffice.The "Detected file type..." error likely indicates that your file variable is not configured properly.
@moncat2005 commented on GitHub (May 6, 2025):
I think there may be some configuration errors on my part.
Could you please help point them out?
Thank you.
My workflow configuration starting node is as follows:
From the final execution error, it seems that the starting node reported an error.
I am currently in version 1.2.0, do I need to upgrade to dify version 1.3.1?
@hjlarry commented on GitHub (May 6, 2025):
Your configuration looks fine, but it's difficult to pinpoint the issue without debugging. You might try:
.doc.@moncat2005 commented on GitHub (May 6, 2025):
Thank you very much for your guidance!
Based on your guidance, I have specified the formats doc for other file types.
The test no longer reports errors, and the process can proceed.
It seems that the recognition of DOC format uploaded files is missing in the starting node function of dify1.2.0.
I will upgrade to 1.3.1 later and verify the recognition function of the starting node for the default doc file format again.
@moncat2005 commented on GitHub (May 6, 2025):
Confirmation information:
After upgrading to version 1.3.1 of dify, configure the upload file format on the start node to select the default file format for various types (including doc format).
When uploading the DOC format file again and executing the workflow, it has been processed normally and no more errors are reported.