| Age | Commit message (Collapse) | Author |
|---|
|
|
|
|
|
...and pass it to BazelCasClient
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
...with direct access to mutable fields and drop additional deep copies.
|
|
|
|
|
|
|
|
...and remove ContentBlob.
|
|
|
|
...since it works with ArtifactBlobs only.
|
|
|
|
|
|
|
|
|
|
|
|
...and drop testing of invalid digests since ArtifactDigest always guarantees to hold a valid digest.
|
|
|
|
|
|
|
|
|
|
|
|
...and remove extra method.
|
|
|
|
|
|
|
|
...and while there, pass digests needed to be read by pointer to IncrementalReader to avoid an extra copy.
|
|
|
|
|
|
|
|
...with explicit std::unordered_set.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
While there, also check for availability first, to avoid duplicated
error messages (from git_cas and the caller).
|
|
Trying to access a git object return a recoverable failure, hence
the failure to find the object in the git object database should
be logged at warning level at most. Moreover, in some cases we
should log that event at an even lower level, e.g., if we're just
checking the presence of the object in the local git cas to avoid
unnecessary network access.
|
|
... and, when asked if an artifact is available, also inspect the
git cas.
|
|
|
|
...and employ it in LocalApi.
|
