-
-
Notifications
You must be signed in to change notification settings - Fork 1.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
2.13 crashed with AttributeError: 'Call' object has no attribute 'name' #5969
Comments
@orSolocate This is a regression in the new checker you added. Are you willing to take look? Please feel free to say no, then somebody else will take a look! |
@DanielNoord - thanks for letting me know. I will try to reproduce it with some other node which |
This code was the one I used to reproduce this issue: def format_manifest_serializer_errors(errors):
errors_messages = []
for key, value in errors.items():
for message in format_manifest_serializer_errors(value):
error_message = f"{key}: {message}"
errors_messages.append(error_message)
return errors_messages |
This reverts commit da7461c.
It seems, the problem file is diofant/polys/factortools.py and related to the Unfortunately, tracebacks from parallel runs aren't very helpful. Even the problem file is missing, c.f. this run with -j1. I would consider this as an issue. (I've not found related bugreports so far.) Or is this a feature? |
No the report not being generated while running in parallel is an issue. Probably due to multiple threads writing the same file together as we try to create only one file (?) The error message saying why we can't write not being shown is also an issue but this should be easy to fix in 2.13.1. |
… the list/dict/set being iterated through is a function call.
I uploaded a fix for that. added your example as a regression test and also verified the |
Bug description
I got the following traceback from the project CI:
Configuration
Command used
Pylint output
Expected behavior
No crash
Pylint version
OS / Environment
No response
Additional dependencies
No response
The text was updated successfully, but these errors were encountered: