oci

The doc says

	// Unlike io.Writer.Write, Endpoint.Write transfers ownership of any bytes
	// successfully written to the Endpoint. That is, if a call to
	// Write(SlicePayload{data}) returns (n, err), it may retain data[:n], and
	// the caller should not use data[:n] after Write returns.

but the signature of Write has since changed. It no longer accepts a slice payload, so this

Maybe new warnings after upgrading ErrorProne in #3355.

/home/runner/work/jib/jib/jib-core/src/main/java/com/google/cloud/tools/jib/image/json/JsonToImageTranslator.java:250: warning: [UnrecognisedJavadocTag] This Javadoc tag wasn't recognised by the parser. Is it malformed somehow, perhaps with mismatched braces?
58

59
   * Converts a map of volumes strings to a set of {@link Absolut

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

right now, there are like 5 different places that need updating if we add a new config/cli field:
pkg/config/config.go to add it to the structure
pkg/config/template.go to add it to the man page template
internal/criocli/criocli.go to add the cli flag
docs/* and completions/* to add completions and documentation

Ideally, we could have just one (or maybe two) places we add a structure, and t

weaveworks/footloose#259

Why?

Since youki is a container runtime, it is software that should be security-sensitive. Therefore, it should be covered as much as possible by unit tests to avoid bugs as much as possible.
However, because it is a container runtime, it is difficult to write unit tests because it is difficult to handle mocks. In other words, this is a challenge. It is also a chance to design well.
https://

Our current documentation for using templates points users to the JSON output to learn about what data is available to the template author. This is insufficient, because although it currently describes the correct shape of data, it leaves users guessing at the correct casing for field names.

A better source of truth than the JSON output is the

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

In a use case of inserting primarily binary or already compressed objects, having a flag to just disable compression seems feasible.
This would leave the mediaType as just application/vnd.oci.image.layer.v1.tar