Johan Lundberg

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.

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?

Ok, you need to change cypher.default_language_version to 3.1 in neo4j.conf, please see https://github.com/johanlundberg/neo4j-django-tutorial/issues/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"...

Well you can mount a config file from the outside, but that is beside the point now after my last update. Just do a git pull and try the bootstrap...

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).

Can you open a new issue to discuss this problem?

I was hoping to have time to start using requests instead of the standard http lib to see if connection pooling would solve the weirdness I was experiencing. But...as always...

I also merged @prauscher branch to our repo and, with my exception above, have seen no problems. Thanks!

The trouble does not end there sadly as xmlsec1 version 1.2.37 that I get with Debian Stable does not seem to handle the response. ``` error=func=xmlSecTransformRsaOaepReadParams:file=transforms.c:line=2703:obj=unknown:subj=unknown:error=27:unexpected node:node=MGF func=xmlSecOpenSSLRsaOaepNodeRead:file=kt_rsa.c:line=1002:obj=rsa-oaep-mgf1p:subj=xmlSecTransformRsaOaepReadParams:error=1:xmlsec library function...