Mintplex-Labs/anything-llm
1
0
Fork 0
mirror of https://github.com/Mintplex-Labs/anything-llm.git synced 2026-07-19 14:13:35 -04:00
Code Issues 328 Packages Projects Releases 10 Wiki Activity

[GH-ISSUE #2102] [BUG]: Resulting text content was empty for xxx #1369

New Issue
Closed
opened 2026-02-22 18:24:29 -05:00 by yindo · 1 comment
yindo commented 2026-02-22 18:24:29 -05:00
Owner
Copy Link
Copy Source

Originally created by @qiuchen001 on GitHub (Aug 12, 2024).
Original GitHub issue: https://github.com/Mintplex-Labs/anything-llm/issues/2102

How are you running AnythingLLM?

Docker (local)

What happened?

I am uploading two documents, one of them succeeds but the other one fails with a failure log message of:
[collector] info: -- Working 软件设计师教程第5版.pdf --
[backend] info: [Event Logged] - document_uploaded
[collector] error: Resulting text content was empty for 软件设计师教程第5版.pdf.

From the logs, I can't directly deduce what's causing the problem

Initially I wondered if the document was too big, and when I compressed the failed one to the same size as the successful one (16M), it still failed the same way.

Does anyone know what is causing this? How can I circumvent this error?

Are there known steps to reproduce?

No response

Originally created by @qiuchen001 on GitHub (Aug 12, 2024). Original GitHub issue: https://github.com/Mintplex-Labs/anything-llm/issues/2102 ### How are you running AnythingLLM? Docker (local) ### What happened? I am uploading two documents, one of them succeeds but the other one fails with a failure log message of: [collector] info: -- Working 软件设计师教程第5版.pdf -- [backend] info: [Event Logged] - document_uploaded [collector] error: Resulting text content was empty for 软件设计师教程第5版.pdf. From the logs, I can't directly deduce what's causing the problem Initially I wondered if the document was too big, and when I compressed the failed one to the same size as the successful one (16M), it still failed the same way. Does anyone know what is causing this? How can I circumvent this error? ### Are there known steps to reproduce? _No response_
yindo added the possible bug label 2026-02-22 18:24:29 -05:00
yindo closed this issue 2026-02-22 18:24:29 -05:00
yindo commented 2026-02-22 18:24:29 -05:00
Author
Owner
Copy Link
Copy Source

@timothycarambat commented on GitHub (Aug 13, 2024):

Is it possible this document is a scanned PDF and not a generated PDF? the pdf parser does not use OCR https://github.com/Mintplex-Labs/anything-llm/issues/510

@timothycarambat commented on GitHub (Aug 13, 2024): Is it possible this document is a _scanned_ PDF and not a generated PDF? the pdf parser does not use OCR https://github.com/Mintplex-Labs/anything-llm/issues/510
yindo changed title from [BUG]: Resulting text content was empty for xxx to [GH-ISSUE #2102] [BUG]: Resulting text content was empty for xxx 2026-06-05 14:40:23 -04:00
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
Desktop
Docker
Integration Request
Integration Request
OS: Linux
OS: Mobile
OS: Windows
UI/UX
blocked
bug
bug
core-team-only
documentation
duplicate
embed-widget
enhancement
feature request
github_actions
good first issue
investigating
needs info / can't replicate
possible bug
pull-request
Mirrored from GitHub Pull Request
 question
stage: specifications
wontfix
No Label possible 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: Mintplex-Labs/anything-llm#1369
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?