-
-
Notifications
You must be signed in to change notification settings - Fork 188
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.
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
Lookup Tool Stalls #917
Comments
Hi @jaickler Are there any errors in the developer console logs when this happens? Thanks for the report |
Hello! Yes, I was able to check the developer logs and saw the vector sizes didn't match. I deleted the multi folder and then relaunched Obsidian and that fixed half the issue. The other half is that when using OpenAI's 4o-mini model I have to send the tool results in the user message or I also receive errors. I suppose the nature of the current bug is that, at least for 4o-mini the tool results must be sent in the user prompt. |
Thanks for following up. 4o-mini seems to be working with/without sending tools response in the user message. Does toggling that setting on/off consistently produce the same success/fail results for you? Please do let me know if you notice any other patterns or anything that might help narrow down what might be causing the issue 🌴 |
I'm having the same problem with gemini |
I check one more think i opened a new chat and just asked if it can tell me somethink(didn't ask to use vault) and it did answer in lookup only so I don't think it is realed to vault |
Bug
When using smart chat the lookup tool will show hypotheticals and then the loading wheel will display indefinitely.
Expected behavior
Recurve message from LLM after lookup finishes.
How to replicate
Use gpt-4o-mini with tools results being sent in user message or not.
Trigger the lookup tool.
Wait indefinitely for message to return.
Notes
I am using Linux on my laptop and do not have mobile enabled. Embedding have fully loaded already.
The text was updated successfully, but these errors were encountered: