Tom Godkin
Tom Godkin
Noticed it doesn't actually fix #495 lol. I'll take another look later and push over this fork.
> A disadvantage of this is that every Ginkgo user would have the complexity of depending on and downloading the go.uber.org/goleak code even if they are not using the functionality....
Thanks for the pokes! I never got around to working on this and I'm unlikely to find time at least in the near future to work on it I'm afraid.
We're essentially asking for a way to enable `use_hierarchy` for a container's cgroup via the runtime spec, so that containers we create later that use child cgroups share memory limits...
Status history should be considered. See Kubernetes events.
I like this option too, where the Generator is a simple convenience for a stateless Iterator (or where state is captured through a closure). Unlike @dranikpg I think the Generator...
Perhaps simply `iter.New(f) *FuncIter { ... }`
Only `ZipIter` remains, along with documenting which iterators are primary and which are secondary.
Thanks for the suggestion. I'm in two minds about this, I can see this being used, however I'm not sure it's worth adding since users could achieve the same thing...
@geofffranks I'm not able to see the test output from the failure. Lemme know what happened and I'll have a go at fixing it.