Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

LocalDocs error 'item at index 3 is not a prompt' with all models in the reasoning tab. #3445

Closed
QohoZ opened this issue Jan 31, 2025 · 12 comments · Fixed by #3451
Closed

LocalDocs error 'item at index 3 is not a prompt' with all models in the reasoning tab. #3445

QohoZ opened this issue Jan 31, 2025 · 12 comments · Fixed by #3451

Comments

@QohoZ
Copy link

QohoZ commented Jan 31, 2025 •
edited
Loading

I encounter the error 'item at index 3 is not a prompt' with all DeepSeek models in the reasoning tab. If I ask just one question, it works, but if I ask another one, I get that error. I should mention that I was using it with LocalDocs; apparently, that’s when it refuses to respond until the model is reloaded.

Originally posted by @QohoZ in #3404
@frozenproof
Copy link

Im having this exact same issue, still dont know why, it only happens with local docs.

@brammiedema
Copy link

brammiedema commented Feb 1, 2025 •
edited
Loading

I have the same issue, it seems there is a bigger issue where I am also unable to index any fodlers that are not on the C drive on windows 11 24H2 (sadly... the audio issues are insane)

@macroxue
Copy link

macroxue commented Feb 1, 2025 •
edited
Loading

Hit the same issue with v3.8.0 on Linux Mint 21.1. The first prompt works fine but the second gives "Error: item at index 3 is not a prompt".

@iCryptoMaster
Copy link

same issue here works on the first prompt but the second gives that error, running on windows 11 here.

@ilgrank
Copy link

ilgrank commented Feb 1, 2025

Ditto for me on W10 22H2

@indrabagus
Copy link

Same problem with me, running on windows 11

@ThiloteE ThiloteE mentioned this issue Feb 2, 2025
Merged
@MarsSemi
Copy link

MarsSemi commented Feb 3, 2025

Same problem here, using MAC M1 Pro ~

@jaapnb
Copy link

jaapnb commented Feb 3, 2025

Same issue here (Win 11 RTX 4080 CUDA)

@jaapnb
Copy link

jaapnb commented Feb 3, 2025

Might be fixed here: #3451

@HowellHudson
Copy link

Same here on Mac-Mini M4 Pro.
I see it is marked closed with a possible fix.
However, it is unclear when that might be moved into an update.
Am I reading this correctly?

@brammiedema
Copy link

I think when the sprint ends they create a release candidate, after succesfull testing the release candidate will be released as an update/installer. At least this is what i assume with the setup they have here on github.

@cebtenzzre
Copy link
Member

This fix was included in the v3.9.0 release.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

Successfully merging a pull request may close this issue.

Fix index used by LocalDocs when tool calling/thinking is active nomic-ai/gpt4all