-
Notifications
You must be signed in to change notification settings - Fork 26
Exception ignored in: <bound method Connection.del of <neo4j.bolt.connection.Connection object #10
Comments
Below is the traceback: Exception ignored in: <bound method Driver.del of <neo4j.v1.direct.DirectDriver object at 0x1084784a8>> |
Thank you for the traceback. I think that looks very much like a bug in the neo4j-driver module. I will look in to it if I find the time. |
When using migrate command: |
From what I have been able to find this is an exception thrown from the neo4j driver when the connection is already closed. The migration is successful anyway, right? |
Im not sure. When bootstrapping I get this error:
So its not working at least |
Ok, you need to change cypher.default_language_version to 3.1 in neo4j.conf, please see #11. |
I found a usage of the now deprecated START cypher statement. So now the above comment can be disregarded. I still see the Exception TypeError: "'NoneType' object is not callable" in <bound method DirectDriver.del of <neo4j.v1.direct.DirectDriver object at 0x7f3b249a6bd0>> ignored error but the app works as expected, |
I am using Docker though, I can't change the neo4j.conf then, right? |
Well you can mount a config file from the outside, but that is beside the point now after my last update. |
I just ran another docker container with version 3.1 so working now |
However the website is really slow, and cant load the movies or persons page at all. loads forever. does it work for you? |
Yes, it works for me. I just ran through the tutorial with a new clone of the repo and the latest Neo4j docker image (3.2.1). |
cloned new repo and ran it just like you, but I still cant get into the movies or persons page on the website. The homepage and admin page works fine though |
Can you open a new issue to discuss this problem? |
Looking at the __del__ logging exception error messages generated by the bootstrap step. It's probably benign because it only happens at the end of the program during the final garbage collection. It's still disconcerting though. It looks like the exception and message could be avoided by adding the following line at the bottom of the bootstrap.py file:
with indention to indicate it's the last line of that final method. There's a similar message when one ctrl-c's out of the runserver step. It looks like it would be much more difficult to eliminate that and less disconcerting. The best solution might be to ask the Neo4j team to evaluate if that exception passing through the Driver.__del__() method is always benign. If so they probably should modify __del__() to catch the exception and swallow it. Or modify the close() method to check for parameters that have already been GC'd so as to avoid generating the exception in the first place. |
@brajaram Was there no more output, like a traceback?
The text was updated successfully, but these errors were encountered: