Mintplex-Labs/anything-llm
1
0
Fork 0
mirror of https://github.com/Mintplex-Labs/anything-llm.git synced 2026-07-21 01:25:28 -04:00
Code Issues 328 Packages Projects Releases 10 Wiki Activity

[GH-ISSUE #1291] [BUG]: Error: 1 documents failed to add. #813

New Issue
Closed
opened 2026-02-22 18:21:30 -05:00 by yindo · 4 comments
yindo commented 2026-02-22 18:21:30 -05:00
Owner
Copy Link
Copy Source

Originally created by @3SMMZRjWgS on GitHub (May 6, 2024).
Original GitHub issue: https://github.com/Mintplex-Labs/anything-llm/issues/1291

How are you running AnythingLLM?

AnythingLLM desktop app

What happened?

When I try to embed the attached PDF (it's a public document): ConEd - Climate Change Vulnerability Study - 20230901.pdf, I receive the following error:

Error: 1 documents failed to add.
Invalid argument error: Values length 26624 is less than the length (1024) multiplied by the value size (1024) for FixedSizeList(Field { name: "item", data_type: Float32, nullable: true, dict_id: 0, dict_is_ordered: false, metadata: {} }, 1024)

Similar errors show up on other large (> 150 pages) PDFs I've tested. One apparent solution is to manually segment a PDF to smaller (~50 pages) PDFs. Is this error caused by my embedding model settings in the Anything LLM app or some other reason(s)?

Below is a screenshot of the embedding model settings in AnythingLLM:

Screenshot 2024-05-05 213607

I'm using AnythingLLM Windows Desktop App 1.5.3 installed on Windows 11 Pro. I'm using Ollama 0.1.33 as the backend for LLMs and embedding models.

Are there known steps to reproduce?

Simply download the attached PDF, load it into AnythingLLM, and try to embed it using mxbai-embed-large provided by Ollama.

Originally created by @3SMMZRjWgS on GitHub (May 6, 2024). Original GitHub issue: https://github.com/Mintplex-Labs/anything-llm/issues/1291 ### How are you running AnythingLLM? AnythingLLM desktop app ### What happened? When I try to embed the attached PDF (it's a public document): [ConEd - Climate Change Vulnerability Study - 20230901.pdf](https://github.com/Mintplex-Labs/anything-llm/files/15215947/ConEd.-.Climate.Change.Vulnerability.Study.-.20230901.pdf), I receive the following error: ``` Error: 1 documents failed to add. Invalid argument error: Values length 26624 is less than the length (1024) multiplied by the value size (1024) for FixedSizeList(Field { name: "item", data_type: Float32, nullable: true, dict_id: 0, dict_is_ordered: false, metadata: {} }, 1024) ``` Similar errors show up on other large (> 150 pages) PDFs I've tested. One apparent solution is to manually segment a PDF to smaller (~50 pages) PDFs. Is this error caused by my embedding model settings in the Anything LLM app or some other reason(s)? Below is a screenshot of the embedding model settings in AnythingLLM: <img width="723" alt="Screenshot 2024-05-05 213607" src="https://github.com/Mintplex-Labs/anything-llm/assets/63822843/263734dc-960e-43eb-ab87-f611d2e8052c"> I'm using AnythingLLM Windows Desktop App 1.5.3 installed on Windows 11 Pro. I'm using Ollama 0.1.33 as the backend for LLMs and embedding models. ### Are there known steps to reproduce? Simply download the attached PDF, load it into AnythingLLM, and try to embed it using mxbai-embed-large provided by Ollama.
yindo added the possible bug label 2026-02-22 18:21:30 -05:00
yindo closed this issue 2026-02-22 18:21:30 -05:00
yindo commented 2026-02-22 18:21:31 -05:00
Author
Owner
Copy Link
Copy Source

@RahSwe commented on GitHub (May 6, 2024):

Does the server have enough RAM?

@RahSwe commented on GitHub (May 6, 2024): Does the server have enough RAM?
yindo commented 2026-02-22 18:21:31 -05:00
Author
Owner
Copy Link
Copy Source

@help4bis commented on GitHub (May 6, 2024):

Tested upload on my server, it works fine. Try to increase your token context window.

Chat Model INstalled
gfg/solar-10b-instruct-v1.0
Token Context Window
256000

Server has no GPU has 49Gb of memory, so not something really big.

@help4bis commented on GitHub (May 6, 2024): Tested upload on my server, it works fine. Try to increase your token context window. Chat Model INstalled gfg/solar-10b-instruct-v1.0 Token Context Window 256000 Server has no GPU has 49Gb of memory, so not something really big.
yindo commented 2026-02-22 18:21:31 -05:00
Author
Owner
Copy Link
Copy Source

@3SMMZRjWgS commented on GitHub (May 6, 2024):

Tested upload on my server, it works fine. Try to increase your token context window.

Chat Model INstalled gfg/solar-10b-instruct-v1.0 Token Context Window 256000

Server has no GPU has 49Gb of memory, so not something really big.

Thank you for the tip on the context window enlargement. I can confirm a larger context window appears to have solved the error. However, I'm not understanding this: if mxbai-embed-large has a recommended context window of 512, can we experience loss in information during embedding by forcing a larger context window to 256k?

@3SMMZRjWgS commented on GitHub (May 6, 2024): > Tested upload on my server, it works fine. Try to increase your token context window. > > Chat Model INstalled gfg/solar-10b-instruct-v1.0 Token Context Window 256000 > > Server has no GPU has 49Gb of memory, so not something really big. Thank you for the tip on the context window enlargement. I can confirm a larger context window appears to have solved the error. However, I'm not understanding this: if mxbai-embed-large has a recommended context window of 512, can we experience loss in information during embedding by forcing a larger context window to 256k?
yindo commented 2026-02-22 18:21:31 -05:00
Author
Owner
Copy Link
Copy Source

@timothycarambat commented on GitHub (May 6, 2024):

Thank you for the tip on the context window enlargement. I can confirm a larger context window appears to have solved the error. However, I'm not understanding this: if mxbai-embed-large has a recommended context window of 512, can we experience loss in information during embedding by forcing a larger context window to 256k?

Yes, you should not try to embed chunks longer than the recommended token context window. Some models will allow it but the vector search after the fact will not perform as you would expect and you will get worse results or information will be lost. We cannot get the context length from the model or the provider as none show it - so that field is important to be correct, but we cant fill it in for you

@timothycarambat commented on GitHub (May 6, 2024): > Thank you for the tip on the context window enlargement. I can confirm a larger context window appears to have solved the error. However, I'm not understanding this: if mxbai-embed-large has a recommended context window of 512, can we experience loss in information during embedding by forcing a larger context window to 256k? Yes, you should not try to embed chunks longer than the recommended token context window. Some models will allow it but the vector search after the fact will not perform as you would expect and you will get worse results or information will be lost. We cannot get the context length from the model or the provider as none show it - so that field is important to be correct, but we cant fill it in for you
yindo changed title from [BUG]: Error: 1 documents failed to add. to [GH-ISSUE #1291] [BUG]: Error: 1 documents failed to add. 2026-06-05 14:37:20 -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#813
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?