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

[remote] upload: treat ALREADY_EXISTS as success #17692

Closed

Conversation

Yannic
Copy link
Contributor

@Yannic Yannic commented Mar 8, 2023

If the service returns an ALREADY_EXISTS error, then we assume that the proper file is present remotely.

Prior art: #12112

Fixes #12111

If the service returns an `ALREADY_EXISTS` error, then we assume that
the proper file is present remotely.

Prior art: bazelbuild#12112

Fixes bazelbuild#12111
@Yannic Yannic requested a review from a team as a code owner March 8, 2023 17:50
@Yannic
Copy link
Contributor Author

Yannic commented Mar 8, 2023

@tjgq @Wyverald PTAL

@ShreeM01 ShreeM01 added team-Remote-Exec Issues and PRs for the Execution (Remote) team awaiting-review PR is awaiting review from an assigned reviewer labels Mar 8, 2023
@coeuvre coeuvre added awaiting-PR-merge PR has been approved by a reviewer and is ready to be merge internally and removed awaiting-review PR is awaiting review from an assigned reviewer labels Mar 9, 2023
@copybara-service copybara-service bot closed this in daa3dbe Mar 9, 2023
@brentleyjones
Copy link
Contributor

@coeuvre Is this safe for 6.2?

@Yannic
Copy link
Contributor Author

Yannic commented Mar 9, 2023

@bazel-io fork

@Yannic Yannic deleted the yannic-cas-upload-already-exists branch March 9, 2023 16:22
@Yannic
Copy link
Contributor Author

Yannic commented Mar 9, 2023

@bazel-io flag

@bazel-io bazel-io added the potential release blocker Flagged by community members using "@bazel-io flag". Should be added to a release blocker milestone label Mar 9, 2023
@sgowroji sgowroji removed the awaiting-PR-merge PR has been approved by a reviewer and is ready to be merge internally label Mar 10, 2023
@coeuvre
Copy link
Member

coeuvre commented Mar 10, 2023

@bazel-io fork 6.2.0

@bazel-io bazel-io removed the potential release blocker Flagged by community members using "@bazel-io flag". Should be added to a release blocker milestone label Mar 10, 2023
ShreeM01 pushed a commit to ShreeM01/bazel that referenced this pull request Mar 10, 2023
If the service returns an `ALREADY_EXISTS` error, then we assume that the proper file is present remotely.

Prior art: bazelbuild#12112

Fixes bazelbuild#12111

Closes bazelbuild#17692.

PiperOrigin-RevId: 515339566
Change-Id: Iafdd288148e47197cc047d39c9a5e5b6c95acee1
ShreeM01 added a commit that referenced this pull request Mar 13, 2023
If the service returns an `ALREADY_EXISTS` error, then we assume that the proper file is present remotely.

Prior art: #12112

Fixes #12111

Closes #17692.

PiperOrigin-RevId: 515339566
Change-Id: Iafdd288148e47197cc047d39c9a5e5b6c95acee1

Co-authored-by: Yannic Bonenberger <[email protected]>
fweikert pushed a commit to fweikert/bazel that referenced this pull request May 25, 2023
If the service returns an `ALREADY_EXISTS` error, then we assume that the proper file is present remotely.

Prior art: bazelbuild#12112

Fixes bazelbuild#12111

Closes bazelbuild#17692.

PiperOrigin-RevId: 515339566
Change-Id: Iafdd288148e47197cc047d39c9a5e5b6c95acee1
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.

Bazel should accept ALREADY_EXISTS for byte stream uploads
6 participants