-
Notifications
You must be signed in to change notification settings - Fork 1.4k
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
[BUG] NanoGraphRAG TypeError: 'NoneType' object is not subscriptable #504
Comments
Hmm, I see another error in the UI. Under Files->Upload Info windows, after I upload new Files for Nano, I see this error at the bottom of the window:
The docker runtime terminal of the Kotaemon app does not have this kind of error. Here is what I see at the end of its output after uploading files for Nano:
|
Hi, we have that kind of error too. There is a FAQ about it https://github.com/gusye1234/nano-graphrag/blob/main/docs/FAQ.md |
Interesting. I was using the default llama3.1:8b. I'll retest with qwen2.5:14b. |
OK, I re-tested with Qwen and the EmptyNetworkError went away. A different error appears in the UI after indexing, but the file does look to be indexed. Below is the snippet. What is your setup? I'm curious if you have setup the NanoGraphCollection differently than me.
|
Description
I'm running NanoGraphRAG via docker against local Ollama. I pulled the
main-full
docker image this morning ... it was tagged as 10 days old.I run this image with
USE_NANO_GRAPHRAG=true
but saw an error, so I installed Nano via the Readme.Simple reasoning Chats with File Collection backed by Ollama work. The Information Panel is populated with indexed docs.
Chat with NanoGraphRAG Collection errors out in the UI. I've pasted the log below. The error ends with:
TypeError: 'NoneType' object is not subscriptable
What else can I check for finding out the root cause of this?
Reproduction steps
Screenshots
![DESCRIPTION](LINK.png)
Logs
Browsers
Firefox
OS
Linux
Additional information
I've tried with 2 different PDF files.
The text was updated successfully, but these errors were encountered: