-
Notifications
You must be signed in to change notification settings - Fork 1.7k
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
Naive query fails with "'NoneType' object is not subscriptable" #306
Comments
遇到同样问题 |
Do you have a more detailed log? I haven't been able to identify this issue based on the current logs. |
Same Issue. Any solution to this? I am using llama3 and nomic-embed-text. I have changed the context length for llama3 to 32768 as well. INFO:httpx:HTTP Request: POST http://localhost:11434/api/chat "HTTP/1.1 200 OK" |
I have the same error. From both of our logs, it seems like
|
I'm experiencing the same issue where entities don't seem to be extracted correctly - leading to the missing reseponse when querying File "/home/mpc/github/LightRAG/lightrag/operate.py", line 996, in <lambda>
key=lambda x: x["content"],
~^^^^^^^^^^^
TypeError: 'NoneType' object is not subscriptable I've tried just running |
Rolling back to the last version on PIP and not installing from source resolved my issues |
Thanks for sharing! What was the last version of PIP you used? Which models did you use specifically for text generation and embedding generation? Did you set the context length of your model to 32,768? |
`import os from lightrag import LightRAG, QueryParam WORKING_DIR = "./dickens" if not os.path.exists(WORKING_DIR): rag = LightRAG( with open("story.txt", "r", encoding="utf-8") as f: Perform naive searchprint( Perform local searchprint( Perform global searchprint( Perform hybrid searchprint( I am using google Colab and also tried locally but also getting same error TypeError Traceback (most recent call last) 7 frames TypeError: 'NoneType' object is not subscriptable |
使用naive模式的查询结果: |
Same with me. Recent changes made to main branch may have caused this issue. |
Same with me |
same with me, I roll back to commit 186cd34 (2024-11-14) then |
When issuing a naive query like this:
This fails with:
Running a local, global or hybrid query works fine.
This seemed to be introduced with the changes deployed on 19 Nov (UK time)
The text was updated successfully, but these errors were encountered: