-
-
Notifications
You must be signed in to change notification settings - Fork 153
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
it seems Vault QA doesn't work? #475
Comments
What additional information can you provide? Is your network connection setup? Launch the console and you look at the network and console section to make sure nothing is there. Also to note, I am not a contributor. But I feel like you need to provide some more context to your situation. |
the network is fine, but the model's answer is not related to my vault, it seems RAG workflow doesn't work correctly. |
You need to provide a bit more information as It works for me personally. What is your setup? Local ollama or OpenAI? What models are you using? Have you updated the plugin to the latest version? Have you indexed your notes recently? Basically, we need information about how you are using it or else, no one can help you. |
I have the same issue. Fairly new Obsidian install. Ollama setup on my Macbook Pro M3. I tried llama3 and gemma2. Plugin version 2.5.2. Indexing is set to "On Mode Switch", but I also clicked the button to manually refresh vault indexing.
|
I did some digging. For me all files were filtered out because of this line:
mtime always had the same value as latestMtime. not sure where this issue comes form though... |
I tried to ask a question based on a note in my vault, but Model didn't know anything about my question
The text was updated successfully, but these errors were encountered: