Currently validating checksums requires lots of knowledge on the part of the caller. We should expose optional checksum validation in our existing validation functions e.g. IPv4.IsValid.

header.UDP and header.TCP don't currently have these functions; we should add them.

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

cri-o/cri-o#4409 changed the function names of the completions, but didn't update the script that generated the completions. I should have reviewed more thoroughly, and we should have checked the pipeline results. oops 😄

We need to update internal/criocli/completions.go to be able to handle two different set of names (and the other small nits in that PR)

succ

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)
...