Aaron Lehmann

Results 29 issues of Aaron Lehmann

Instead of letting the cache grow without bound, use a LRU to impose a size limit. The limit is configurable through a new `blobdescriptorsize` config key.

This simple change mainly affects the distribution client. By respecting the context the caller passes in, timeouts and cancellations will work as expected. Also, transports which rely on the context...

When the "redirect" option is set to true, it applies to both `HEAD` and `GET` requests for blobs. The use case for `GET`s makes sense - this avoids the registry...

See https://github.com/golang/go/issues/27505 for context. `Pdeathsig` isn't safe to set without locking to the current OS thread, because otherwise thread termination will send the signal, which isn't the desired behavior. I...

This adds an `AddrMismatch` flag to `ProcessRaftMessageResponse`, which allows any node that receives a Raft message to signal to the sender that its address didn't match the expected value. Based...

area/raft

It should be possible to ignore files that should not be represented in the continuity manifest, such as certain device drivers. Support a `--ignore` flag to `continuity build` that allows...

For the sake of completeness, Continuity manifests should include unix sockets. However, it is not generally useful for continuity to create these when applying a manifest. Thus, `apply` and `verify`...

Continuity does not currently verify digests during the `apply` operation. It should be changed to verify them by default. In case the data comes from a trusted source, such as...

The current implementation of `continuity apply` checks an existing directory against a Continuity manifest. A better model would involve specifying a source and destination, so that Continuity creates the target...

There should be some flexibility in choosing what attributes are enforced or verified by `continuity apply` and `continuity verify`. For example, a user may wish to ignore ctime and mtime...