docs: note the conflict-cleanup delete after an unknown upload outcome
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
This commit is contained in:
1 parent
61733fce6e
commit
b440df2e1f
1 file changed
+3
@@ -148,6 +148,9 @@ Small, specific, independently actionable. Remove only when actually done.
|
||||
for any `ConflictDraftRevisionID`, which an active file with a draft
|
||||
revision also reports; Task 11 uploads a new revision in that case
|
||||
instead.
|
||||
A `--retries` pass after an upload whose outcome was unknown can reach
|
||||
the own-draft `delete_multiple` in `resolveConflict` (`upload.go`); it
|
||||
is decided by Proton's conflict details, which could in theory lag.
|
||||
- [ ] protondrive: confirm the HTTP status and code Proton returns for a
|
||||
bad verifier token, a missing block and a stale `CurrentRevisionID`
|
||||
(the fake uses 422 / 2000, which the spec maps to "upgrade rclone").
|
||||
|
||||
Reference in new issue
Block a user