{"push_id":599308014,"size":1,"distinct_size":1,"ref":"refs/heads/master","head":"f0ea8cb26a1279b56aa4ba37f8853f76e9b392c5","before":"c47da3d86a554c363b5b61b67b77e4638fe63dc1","commits":[{"sha":"f0ea8cb26a1279b56aa4ba37f8853f76e9b392c5","author":{"email":"57a33a5496950fec8433e4dd83347673459dcdfc@addthis.com","name":"ian"},"message":"remove TreeMapState.leases + fix nested elements\n\nthe responsibility to release nodes has been moved from a per-bundle\ngarbage collector to the caller of methods that return them. This\ngreatly decreases the number of concurrently leased tree nodes in\nmany cases, although it would be nice if we knew in advance that the\ncollective leaf nodes were not interesting to the root caller (this\ncan be effected with a path element whose filter always fails placed\n\"after\" the leaf nodes, but such an arrangement is inconvenient).\n\nthis also fixes an apparent bug in the processing of sub-groups of\npath elements -- such as those in PathBranch, PathCall, and PathChild.\nIf the last path element in such a sub-group generates multiple nodes\n-- such as a PathValue operating on a value array -- then subsequent\nchild nodes occuring below the sub-group would only be generated for\nthe last parent node to be processed. eg. `{field_a: [a, b], field_b:\n c}` could result in the top level nodes `a` and `b`, but only `b`\n might have a child node `c`.","distinct":true,"url":"https://api.github.com/repos/addthis/hydra/commits/f0ea8cb26a1279b56aa4ba37f8853f76e9b392c5"}]}