With the latest Neo4j server from brew I get this:
Error: [object Object]
at exports.adjustError (node_modules/neo4j/lib/util.js:67:15)
at __$GraphDatabase_prototype_query__14 (node_modules/neo4j/lib/GraphDatabase.js:276:26)
at __tryCatch (node_modules/neo4j/node_modules/streamline/lib/callbacks/runtime.js:141:4)
at ___ (node_modules/neo4j/lib/GraphDatabase.js:274:118)
at ___ (node_modules/neo4j/lib/GraphDatabase.js:255:28)
at Request.___ [as _callback] (node_modules/neo4j/node_modules/streamline/lib/callbacks/runtime.js:85:13)
at Request.init.self.callback (node_modules/request/main.js:120:22)
at Request.EventEmitter.emit (events.js:96:17)
at Request.<anonymous> (node_modules/request/main.js:555:16)
at Request.EventEmitter.emit (events.js:93:17)
I don't know what provoked it, sorry.
Are you able to run the tests without errors? (You just have to cd into the node-neo4j dir and run npm test. You'll need a running db at 7474, and note that it'll add nodes to that db.)
Does this consistently happen or just happened randomly?
If I reload the browser I don't see the bug. I'll dig in and see which code line of mine causes it...
My login functionality causes it. So yes, I would say it's consistent.
Test seems to fail:
$ npm test
> email@example.com test node_modules/neo4j
> _coffee test
passed gremlin tests
passed CRUD tests
TypeError: Property '0' of object node @13,node @12,node @10 is not a function
at ___ (node_modules/neo4j/test/cypher._coffee:196:5290)
at ___ (node_modules/neo4j/node_modules/streamline/lib/callbacks/runtime.js:85:13)
at GraphDatabase_prototype_query__14 (node_modules/neo4j/lib/GraphDatabase.js:276:56)
at main (node_modules/neo4j/test/cypher._coffee:153:12)
npm ERR! Test failed. See above for more details.
npm ERR! not ok code 0
Hmm, I wonder if the tests are just failing because the Cypher queries need to be updated for any breaking changes in 1.8. I'll try to upgrade us to 1.8 later this week and investigate this. Thanks for the heads-up!
Oh, are you using an index that doesn't exist, maybe?
Hey @webjay, just checking up on this: are you still seeing this error with the current node-neo4j?
Great to hear.