Stuck on an issue?

Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.

And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.

client.execute not working with Tinkerpop Server 3.2.3…

See original GitHub issue

When running either example code or npm run examples:node, the script seems to start fine and even connect to the socket (throws an error if the server is not running), but client.execute’s callback never gets called.

Tinkerpop Server version is: 3.2.3 and started with: ./bin/gremlin-server.sh conf/gremlin-server-classic.yaml

Node version is: 7.0 (but also tried with v6.9.1: same results).

npm version is: 3.10.8

Connecting to the Tinkerpop Server with gremlin console or through the Python interface works fine.

Issue Analytics

State:
Created 7 years ago
Comments:5 (2 by maintainers)

Top GitHub Comments

2reactions

jbmussocommented, Nov 13, 2016

Actually, it’s not documented but you can supply a path option to the option object when instantiating a client. { path: '/gremlin' } should work.

2reactions

jbmussocommented, Oct 28, 2016

This is related to the connection URL string which now requires to append /gremlin. I need to fix this, hopefully today.

On Friday, 28 October 2016, Victor O. Santos Uceta notifications@github.com wrote:

I’m having the same issue.

— You are receiving this because you are subscribed to this thread. Reply to this email directly, view it on GitHub https://github.com/jbmusso/gremlin-javascript/issues/61#issuecomment-256855997, or mute the thread https://github.com/notifications/unsubscribe-auth/AAMa1Pv5YNhGhgjekN-YJOWF4vfb3UYCks5q4aW5gaJpZM4KjCZr .

Jean-Baptiste