Currently, the kernel wraps the cypher-shell. That is, when the kernel is getting started, a command similar to cypher-shell -u neo4j -p neo4j is executed. That will of course only succeed when a Neo4j instance is running. Otherwise, cypher-shell returns Connection refused and the kernel crashes. That is an issue in case one wants to start notebooks in which one wants to create a Neo4j container only for this notebook, such as in examples/paradise_papers.ipynb.
A possible solution could be to try to run cypher-shell -u neo4j -p neo4j and check if it can connect (or check if a neo4j process is running) and if not to start a small instance in a container and connect to that.
Currently, the kernel wraps the
cypher-shell. That is, when the kernel is getting started, a command similar tocypher-shell -u neo4j -p neo4jis executed. That will of course only succeed when a Neo4j instance is running. Otherwise,cypher-shellreturnsConnection refusedand the kernel crashes. That is an issue in case one wants to start notebooks in which one wants to create a Neo4j container only for this notebook, such as inexamples/paradise_papers.ipynb.A possible solution could be to try to run
cypher-shell -u neo4j -p neo4jand check if it can connect (or check if a neo4j process is running) and if not to start a small instance in a container and connect to that.