-
Notifications
You must be signed in to change notification settings - Fork 2.1k
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
[7.0.3 RC2] Delete same folder twice over webdav, appears twice in trashbin #11910
Comments
This can be reproduced more easily with curl:
|
When using encryption, only one of the folders with contain the correct keys. |
When hammering the server with DELETE calls I managed once to observe that the etag of unrelated files was changed. This one: #11906 I'll try and reproduce this more consistently. |
wow. Crazy bug. |
The etag did not change on deletion, it was a side-effect of my testing. |
Keeping this ticket here to find a quickfix to avoid double deletion. |
Removing from the sprint as we cannot reliably detect this situation. Please evaluate and schedule #11804 instead. |
Transactional locking has been implemented and covers this => close |
Steps to reproduce
Expected result
First delete: possible time out, not a big deal.
Second delete: 404
Third delete: 404
Trash bin has one folder "subdir"
Actual result
First delete: time out.
Second delete: 403 ?!
Third delete: 404
Trash bin has TWO folders "subdir" with the same contents
Versions
ownCloud 7.0.3 RC2
Android client 1.6.1
Access log
(the folder I deleted was "Berlin")
ownCloud log
I have only reproduced this once when I wanted to delete a folder on my server.
Will try again the next days.
As you can see in owncloud.log, two trashbin folders "Berlin" have been created with a slightly shifted timestamp. The second delete operation did not find the share keys any more because they were possibly already moved to the trashbin.
Also you'll notice that some files were purged from the trashbin, which possibly delayed the deletion operation further.
@schiesbn
The text was updated successfully, but these errors were encountered: