-
Notifications
You must be signed in to change notification settings - Fork 196
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
Data loss during cut&paste cross-space #4114
Comments
Seems to be a backend issue. Web sends the following request for moving a file from a personal space to a project space:
which results in a 404. The corresponding |
@micbar what do you think, fix in ocis/reva or temporarily disable in web? As it can result in data loss this is IMO release blocking. |
@kulmann I will take a look. First impression, looks like a backend problem. |
userfacing crossstorage "move" should be possible - users won't distinguish between a crossstorage and non-crossstorage move I guess (they are used to easily move a file from HDD to a USB stick). The main problem is, that a cross storage move (copy & delete) can take a long time, right? If yes, I'd propose the following:
@micbar would that be the right ui-behaviour? |
Steps to reproduce
ctrl+x
(linux/windows) orcmd+x
(mac) to cut the filectrl+v
(linux/windows) orcmd+v
(mac) to paste the fileExpected behaviour
a) File gets moved successfully OR b) in case of an error the file stays in the original location
Actual behaviour
Apparently cross-space move (internally: copy & delete) is not possible at all or not correctly implemented in web (needs investigation). The much bigger issue in this case is, that the failing move request fails results in data loss: the file doesn't get copied successfully but gets deleted from the original location anyway.
Needs investigation if the two bugs are backend only, frontend only or a mix of both.
Solution
502 Bad Gateway
according to specThe text was updated successfully, but these errors were encountered: