Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[6.0.0] Fsync before rename after copy in DiskCacheClient #16832

Merged
merged 1 commit into from
Nov 23, 2022

Conversation

coeuvre
Copy link
Member

@coeuvre coeuvre commented Nov 23, 2022

Debugging disk_cache at work, found this TODO in the code, decided to implement.

If fsync fails we don't rename to final name — which is the correct error handling as it was before if copy failed.

Closes #16691.

PiperOrigin-RevId: 486901488
Change-Id: Ia2aef6bc196e1d0a61f46b7b6c719563938ff48e

Debugging `disk_cache` at work, found this TODO in the code, decided to implement.

If `fsync` fails we don't rename to final name — which is the correct error handling as it was before if `copy` failed.

Closes bazelbuild#16691.

PiperOrigin-RevId: 486901488
Change-Id: Ia2aef6bc196e1d0a61f46b7b6c719563938ff48e
@coeuvre coeuvre requested a review from ShreeM01 as a code owner November 23, 2022 16:52
@coeuvre coeuvre changed the title Fsync before rename after copy in DiskCacheClient [6.0.0] Fsync before rename after copy in DiskCacheClient Nov 23, 2022
@ShreeM01 ShreeM01 merged commit e0b417a into bazelbuild:release-6.0.0 Nov 23, 2022
@coeuvre coeuvre deleted the cherry-pick-16691 branch November 24, 2022 11:34
@ShreeM01 ShreeM01 added the team-Remote-Exec Issues and PRs for the Execution (Remote) team label Dec 5, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
team-Remote-Exec Issues and PRs for the Execution (Remote) team
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants