summaryrefslogtreecommitdiff
AgeCommit message (Collapse)Author
2025-02-10BazelCasClient: replace ProcessResponseContentsMaksim Denisov
...with direct access to mutable fields and drop additional deep copies.
2025-02-10Rename kMaxBatchTransferSize to MessageLimits::kMaxGrpcLengthMaksim Denisov
2025-02-10MessageLimits: move grpc to private deps.Maksim Denisov
2025-02-10MessageLimits: Add header guardMaksim Denisov
2025-02-10content_git_map: remove unused parametersKlaus Aehlig
2025-02-07Add design document on profiling buildsKlaus Aehlig
2025-02-07Move implementation of ContentBlob to artifact_blobMaksim Denisov
...and remove ContentBlob.
2025-02-07Rename artifact_blob_container to artifact_blobMaksim Denisov
2025-02-07CommonApi: Remove template parameter from UploadAndUpdateContainerMaksim Denisov
...since it works with ArtifactBlobs only.
2025-02-07Remove BazelBlobMaksim Denisov
2025-02-07BazelCasClient: Use ArtifactDigest in FindMissingBlobsMaksim Denisov
2025-02-07BazelCasClient: Use ArtifactDigest in bytestream readingMaksim Denisov
2025-02-07BazelCasClient: Use ArtifactBlob in UpdateSingleBlobMaksim Denisov
2025-02-07BazelCasClient: Use ArtifactBlob in BatchUpdateBlobsMaksim Denisov
2025-02-07BazelCasClient: Use ArtifactDigest in BatchReadBlobsMaksim Denisov
...and drop testing of invalid digests since ArtifactDigest always guarantees to hold a valid digest.
2025-02-07BazelNetwork: Use ArtifactDigests in IsAvailableMaksim Denisov
2025-02-07BazelNetwork: Use ArtifactBlobs in UploadBlobsMaksim Denisov
2025-02-07ByteStreamUtils: Use ArtifactDigestMaksim Denisov
2025-02-07BazelCasClient: Drop iterators in BatchReadBlobsMaksim Denisov
2025-02-07BazelCasClient: Drop iterators in BatchUpdateBlobsMaksim Denisov
2025-02-07BazelCasClient: Drop iterators in FindMissingBlobsMaksim Denisov
...and remove extra method.
2025-02-07BazelNetworkReader: Validate same blobs just once while batching.Maksim Denisov
2025-02-07BaselCasClient: fix possible loss of data in BatchReadBlobs.Maksim Denisov
2025-02-07BazelNetworkReader: Implement validation for ArtifactBlobsMaksim Denisov
2025-02-07BazelNetworkReader: Use ArtifactDigest in IncrementalReaderMaksim Denisov
...and while there, pass digests needed to be read by pointer to IncrementalReader to avoid an extra copy.
2025-02-07BazelNetworkReader: make reading methods that use bazel digest privateMaksim Denisov
2025-02-07BazelNetwork: Drop iterators in DoUploadBlobsMaksim Denisov
2025-02-07Remove ContentBlobContainer and TransformedRangeMaksim Denisov
2025-02-07Replace ArtifactBlobContainer and BazelBlobContainerMaksim Denisov
...with explicit std::unordered_set.
2025-02-07Replace ContentBlobContainer<T> with std::unordered_setMaksim Denisov
2025-02-07BazelNetwork: Use unordered_set in UploadBlobs instead of BazelBlobContainerMaksim Denisov
2025-02-07IExecutionApi: Rename IsAvailable to GetMissingDigestsMaksim Denisov
2025-02-07IExecutionApi: Use unordered_set in IsAvailableMaksim Denisov
2025-02-07Remove logging related to blob splitting form BazelApiMaksim Denisov
2025-02-07BazelCasClient: Use unordered_set in FindMissingBlobsMaksim Denisov
2025-02-07ContentBlob: Support hashingMaksim Denisov
2025-02-07DAG: Drop usage of TransformedRange.Maksim Denisov
2025-02-07Implement BackMapMaksim Denisov
...that is a container of Values mapped to Keys, and supports constant complexity search of a Value by a given Key
2025-02-06logging: switch time stamps to UTCKlaus Aehlig
Time stamps in local time without explicit time zone are ambigious, definitely at the end of daylight saving time. Moreover, even if explicit time zones were given, it is still unconvenient to correctly sort event expressed in different time zones. However, with increased use of `just serve`, logs originating from different machines become the norm. Therefore, normalize all time stamps to UTC (and explicitly state that this is the time zone used).
2025-02-05CHANGELOG: mention local-api fixKlaus Aehlig
2025-02-05Add basic end-to-end test for just-mr gc --drop-onlyKlaus Aehlig
2025-02-05just-mr(1): Document new option --drop-only for gc-repoKlaus Aehlig
2025-02-05just-mr gc-repo: support drop onlyKlaus Aehlig
As opposed to the regular CAS/cache, for the git repository implicit in the repository cache we cannot guarantee that data from older generation is always promoted via hard links. Therefore, a certain amount of data can be duplicated between the repo-cache generations. In order to allow compacting storage to the minimum, add an option to gc-repo to only remove the older generation, without rotating.
2025-02-05Repository garbage collector: support dropping onlyKlaus Aehlig
Add support for repository gargabe collection to only drop the older generations without rotating.
2025-02-05just-mr(1): document the gc-repo subcommandKlaus Aehlig
2025-01-30README: fix reference to tutorial sectionKlaus Aehlig
2025-01-30Add basic introduction on how to set up computed rootsKlaus Aehlig
2025-01-30CHANGELOG: document recent fix to `just-mr gc-repo`Klaus Aehlig
2025-01-30Add an end-to-end test for repeated repository garbage collectionKlaus Aehlig
As only a recent commit made it possible to rotate the repository cache more than once, add a test ensuring two properties. - Repeated repository gc is possible and roots are taken from the rotated generation. - It is possible to fully rotate a root out.
2025-01-29local api: absence of a git api is not a success in retrievingKlaus Aehlig
While there, also check for availability first, to avoid duplicated error messages (from git_cas and the caller).