Blacklist: Escalate a repeated 423 Locked to NormalError #5500 #5548
Conversation
This file contains 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
|
@ckamm, thanks for your PR! By analyzing the history of the files in this pull request, we identified @jturcotte, @ogoffart and @dragotin to be potential reviewers. |
ogoffart
reviewed
Mar 3, 2017
src/libsync/owncloudpropagator.cpp
Outdated
| || (item._httpErrorCode == 423) // "Locked", usually a SoftError | ||
| || (status == SyncFileItem::NormalError | ||
| && item._httpErrorCode != 0 // or non-local error | ||
| #ifdef OWNCLOUD_5XX_NO_BLACKLIST |
There was a problem hiding this comment.
I think we can remove this.
|
👍 |
|
Need to be merged in 2.3 then, right? |
|
CONFLICT (content): Merge conflict in src/libsync/owncloudpropagator.cpp (from jenkins) |
|
Merged manually as 8ef11a3 |
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.
Since this targets 2.3.1 I pointed this PR at master.
We should discuss whether we also want this kind of escalation for other soft errors.