| Age | Commit message (Collapse) | Author |
|---|
|
(cherry-picked from fe4006fce755432b1ae3a273873f3649512c7f94)
|
|
|
|
|
|
|
|
ArtifactBlob rehashes content, there's no way to construct it with a wrong digest.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
... and rename appropriately to reflect contents more precisely
than the generic "common". This separation also disentangles
dependencies a bit.
|
|
And ensure every user obtains HashFunction from corresponding IExecutionApi
|
|
|
|
Although references give an additional information about ownership, they introduce additional design difficulties.
|
|
|
|
|
|
...to remove the unnecessary link between folder name and the logic
of resolve_symlinks_map.
|
|
|
|
...and pass it to BazelCasClient
|
|
...and remove ContentBlob.
|
|
|
|
|
|
|
|
...and drop testing of invalid digests since ArtifactDigest always guarantees to hold a valid digest.
|
|
|
|
|
|
|
|
|
|
...and while there, pass digests needed to be read by pointer to IncrementalReader to avoid an extra copy.
|
|
|
|
|
|
...with explicit std::unordered_set.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
Extend the api to optionally accept a different API for preferred
fetching. This is already supported when fetching to a file path;
therefore, extend to keep the interface symmetric.
|
