summaryrefslogtreecommitdiff
path: root/src/buildtool/file_system/git_repo.cpp
diff options
context:
space:
mode:
authorOliver Reiche <oliver.reiche@huawei.com>2024-08-22 17:07:29 +0200
committerOliver Reiche <oliver.reiche@huawei.com>2024-08-23 12:16:37 +0200
commit56d7eef96baaf8365b258217b866f37159abf552 (patch)
tree4590154cd5d0d9c25fa46541919878c9b8993d9f /src/buildtool/file_system/git_repo.cpp
parent1e5cc37df36204474cedef68486ba8b29492d259 (diff)
downloadjustbuild-56d7eef96baaf8365b258217b866f37159abf552.tar.gz
CasClient: Retry batch update for missing response
The remote execution protocol is a bit unclear about how to deal with blob updates for which we got no response. While some clients consider a blob update failed only if a failed response is received, we are going extra defensive here and also consider missing responses to be a failed blob update. Issue a retry for the missing blobs.
Diffstat (limited to 'src/buildtool/file_system/git_repo.cpp')
0 files changed, 0 insertions, 0 deletions