Description
With the release of the 3.4.9 gremlinpython client all queries are now timing out at 30 seconds regardless of the server timeout specified. This was not the case with the 3.4.8 client.
Steps to Reproduce
- Set the Gremlin Server timeout to 60 seconds
- Add a graph with loops
- Install gremlinpython 3.4.8
- Run Test Code and it times out in 60 seconds with an error message from the server like this
{{A timeout occurred during traversal evaluation of [RequestMessage
Unknown macro: {, requestId=450b1b70-49af-409c-9838-826fce6a1634, op='bytecode', processor='traversal', args=
}}
] - consider increasing the limit given to evaluationTimeout}}
- Install gremlinpython 3.4.9
- Run Test Code and it times out in 30 seconds with an error message from the client like this
Operation timed out after 30 seconds
Add Graph Code
g.addV('test').property('id', 1)
g.addV('test').property('id', 2)
g.addE('loop').from(V().has('id', 1)).to(V().has('id', 2))
g.addE('loop').from(V().has('id', 2)).to(V().has('id', 1))
Test Code
from gremlin_python import staticsfrom gremlin_python.structure.graph import Graphfrom gremlin_python.process.graph_traversal import }}{{from gremlin_python.process.anonymous_traversal import traversalfrom gremlin_python.process.traversal import *from gremlin_python.driver.driver_remote_connection import DriverRemoteConnectionfrom gremlin_python.process.traversal import Tconnection = DriverRemoteConnection('ws://localhost:8182/gremlin', 'g')g = traversal().withRemote(connection)try:print(g.V(0).repeat(}}{{.out()).next())except Exception as e:print(e)