anchor.diff:  
   [gremlin-groovy,modern]
   ----
  -t = g.V(1).outE().group().by(label).by(inV());null
  +t = g.V(1).outE().
  +      group().
  +        by(label).
  +        by(inV());null
   t.next()
   ----
   
  
positive.code: 
  image:gremlin-console-ide.png[float=left,width=300] The first line assigns the `Traversal` to `t`, but the line itself
  is actually two lines of code as denoted by the semi-colon. The line of execution actually returns `null`, which is
  what the console actual auto-iterates. At that point you can work with `t` as you desire.
  
  Turning your attention back to the original problem, you can now think about the issue with the `Traversal` not
  containing the appropriate number of vertices in the context of iteration. In the original `Traversal` the second
  
negative.code: 
  public final class Traversals {
    public static Map<String,List<Vertex>> groupAround(GraphTraversalSource g, long vertexId) {
      return g.V(vertexId).outE().
               group().
                 by(label).
                 by(inV()).next()
    }
  }
  ----
  