Per the example in https://godoc.org/github.com/google/go-cmp/cmp#Diff the form should be:

if diff := cmp.Diff(want, got); diff != "" {
    t.Errorf("MakeGatewayInfo() mismatch (-want +got):\n%s", diff)
}

however, NUD tests (and possibly others) are littered with the reverse, e.g.:
https://github.com/google/gvisor/blob/8fa18e8ecb3e3da2015e5c73db9e46494dcfeff7/pkg/tcpip/stack/neighbo

There are a lot of places in libcontainer/cgroups/fs where the usage of writeFile function can be optimised. For example here https://github.com/opencontainers/runc/blob/master/libcontainer/cgroups/fs/blkio.go#L44-L51
the function call to writeFile is made for each entry in the slice BlkioWeightDevice, which in turn opens and closes file for each entry. This can be optimised by joining al

Description
While setting up Cilium 1.8 according to their official documentation on a fresh Kubernetes 1.18 dual-stack cluster with cri-o 1.18.2, I've noticed that the provided connectivity test pods by Cilium 1.8 kept failing their liveness/readiness probes and ended up cra

make tidy currently runs directly on your host relying on the tools and their respective versions. While there is make tidy-in-docker, it is not documented. Let's either replace make tidy in the documentation with make-tidy-docker or change the functionality of make tidy to be containerized.

Per opencontainers/image-spec#803 using zstd compression seems to be on peoples minds.

After reading about it, it seems it's been designed with parallelism in mind, among just being faster on a single core as well. I think it would definitely speed up some of our use cases, at least.

To repro the issue use an image that is not fully qualified as seen below.

 1 ❯ oras push test:test .
panic: runtime error: slice bounds out of range

goroutine 1 [running]:
github.com/deislabs/oras/vendor/github.com/containerd/containerd/reference.Spec.Hostname(0xc000022bb0, 0x9, 0x0, 0x0, 0x147b544, 0xc0001db788)
...