Throw exception if withRemote() is called multiple times during configuration
This is a change in behavior. Prior to this we would have quietly closed the
connection, but that's a little too sneaky. Also, the connection was being
assigned to the current TraversalSource as well as the clone. Not
Throw exception if withRemote() is called multiple times during configuration
This is a change in behavior. Prior to this we would have quietly closed the
connection, but that's a little too sneaky. Also, the connection was being
assigned to the current TraversalSource as well as the clone. Not
Throw exception if withRemote() is called multiple times during configuration
This is a change in behavior. Prior to this we would have quietly closed the
connection, but that's a little too sneaky. Also, the connection was being
assigned to the current TraversalSource as well as the clone. Not
Repository: tinkerpop
Updated Branches:
refs/heads/master 5f912eab0 -> 74930a998
Throw exception if withRemote() is called multiple times during configuration
This is a change in behavior. Prior to this we would have quietly closed the
connection, but that's a little too sneaky. Also, the
Repository: tinkerpop
Updated Branches:
refs/heads/tp32 3be3550d1 -> 0bd9b5ae7
Throw exception if withRemote() is called multiple times during configuration
This is a change in behavior. Prior to this we would have quietly closed the
connection, but that's a little too sneaky. Also, the
Repository: tinkerpop
Updated Branches:
refs/heads/tp33 445a8bf0b -> ffb8c3e4e
Throw exception if withRemote() is called multiple times during configuration
This is a change in behavior. Prior to this we would have quietly closed the
connection, but that's a little too sneaky. Also, the