Details
-
Bug
-
Status: Open
-
Major
-
Resolution: Unresolved
-
3.4.12
-
None
-
None
Description
GraphStep retains the iteratingSupplier from the object it cloned. Typically, this is no problem because at strategy application a graph will replace GraphStep with its own implementation (e.g. TinkerGraph does this with TinkerGraphStep). However, if it is not replaced that iteratingSupplier will refer to the one from the original GraphStep and if strategies have not been applied and if that GraphStep belonged to an anonymous traversal, it will put the clone in a state where it will try to access EmptyGraph rather than the graph instance expected.