-
Notifications
You must be signed in to change notification settings - Fork 2.1k
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]: AttributeError: 'list' object has no attribute 'on_error' #1505
Comments
@NathanAP I created a graphrag project this morning and am running in the same problem. My steps are below and mostly from the getting started steps...
Other than running the index first and failing once due to not having the correct settings, it is pretty clean repro steps Additional information:
|
@NathanAP, my problem seemed to resolve itself once I uncommented and set the api_version values in the settings.yaml file. That said, I still think the run.py file will always error if callbacks is a list. Perhaps type check/handling would be good here or another look.
|
In my case I'm using always the same file(s) to index it because we're using Playwright to make some end to end tests. This morning I got 3 times in a row this same error and then never happened again... TBH I have no idea if this is in our control to manage. |
me too |
same here, i just updated and found this bug. This bug lasted for around 2 hours and now it disappeared, as if it never happened. :) |
Can someone with this error upload an indexing-engine.log so we can see the stack trace? I had the error myself yesterday with a largish dataset, and it was due to too many API requests (mine was on Azure OpenAI). It does not seem consistency, so may be temporary instability issues? |
@natoverse settings.yaml
graphrag 1.0 does not call the api_base inside llm, and uses the default api_base of openai, resulting in model authentication errors,The error log is as follows: |
I've just setup Graphrag and was seeing this trying to go through the Getting Started example. I did review the indexing-engine.log and found a couple of things: My initial problem was the my deployments string was incorrect. This was resulting in a 404 error the request to do the chat completion while extracting the graph - The full URL with the issue was in the and I compared it to a working URL I had from test code and found my issue (I had the deployment name incorrect -- I was using the azure resource name and it needed to be the openai deployment name (in my case gpt-4_1 (I'm using azure openai). I got thorough that and it make it further but I started getting it later in the process, but now I'm seeing a 429 error (rate limit error) For references both case ended up with the list error in the -- but that looks like a secondary error that occurred while processing another error. In my case the first error was a key error on the key 'name' I'm suspecting that the call to the LLM fails and so there is no data, which causes the key error (and then the list error occurs during the handling of the key error) |
Refer to this fix |
same error, how to fix it? |
yeah guys me too fr fr |
the same error for me... |
Below is my indexing.log, it is clean as I only run it once. I am using gpt-4o from openai and the document is about some video description. @natoverse |
@YepJin I also notice that the Key error seems to be for the entire string (everything between the single quotes), so maybe this is an issue in some entry in the settings.yaml? Are these items (e.g. "LOW AUTHENTIC VIDEO", etc) configured as there in some way or in a format that it can't handle properly or doesn't like (are these your entity types?) ... its seems to be taking what looks like it should several different entries and treating it as one item |
I used my own prompts and not limit the entity types. It worked perfectly before I update it (previously I used the version without Drift search).
|
[Bug]: AttributeError: 'list' object has no attribute 'on_error' Just change two things in settings.yaml: Add llm in embeddings as follows: Thanks to Engineer Yang Qi for his efforts. |
this can happend if your api key is not valid for accessing the embedding api. try generating a new key in OpenAI and retrying ---- this will be evident in the log file |
Hmm but then this error would be consistent, wouldn't? I'm getting this error 30% of my index attempts, its not happening everytime. Seems like some instability |
@NathanAP Sounds like a rate limiting issue? |
Seems like a bug in GraphRag code. I'm always using the same files. |
有解决了这个问题的friend吗? |
We believe this was a bug introducing during our adoption of fnllm as the underlying LLM library. We just pushed out a 1.0.1 patch today, please let if know if your problem still exists with that version. |
🔥修改代码就可以解决 https://youtu.be/GRZ2th6s7uY |
This issue has been marked stale due to inactivity after repo maintainer or community member responses that request more information or suggest a solution. It will be closed after five additional days. |
Do you need to file an issue?
Describe the bug
Sometimes when I try to
build_index
, I'm getting the following:Not sure if there's anything I can do to fix it in my side...
Steps to reproduce
This is happening very rarely, tbh. I didn't find a consist that makes it appear.
Expected Behavior
Index should be done normally.
GraphRAG Config Used
Logs and screenshots
No response
Additional Information
The text was updated successfully, but these errors were encountered: