Draft
Conversation
if those are blocking other deletions they have no right to be kept. This is per se only a problem if clone split was not fast enough, which means the volume is short-lived (aka qualifies for force delete) Change-Id: I6fd0ea9e45d7bf6bada6372da9b7dc5295bbf8f4
ec45a7a to
870ec4b
Compare
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
sapcc: purge clones from recovery queue
if those are blocking other deletions they have no right to be kept.
This is per se only a problem
if clone split was not fast enough, which means
the volume is short-lived
(aka qualifies for force delete)