You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Please use the 👍 reaction to show that you want to have the same feature implemented.
Please don't comment if you have no relevant information to add. It's just extra noise for everyone subscribed to this issue.
Subscribe to receive notifications on status change and new comments.
Feature description
When we move some files/placeholders within the structure of the local sync folder, we might end up not being able to upload them to a new location on the server. The most recent case that I've encountered was with a user trying to move many files/folders from someone else's folder to the user's home folder. Since the user did not have enough space in the home folder on the server and received a lot of 507 errors, files were not uploaded to a new location on the server but stayed in a new location in the user's local folder.
We need to implement the roll-back mechanism so the file would get moved to its original location locally if the move has failed. The desktop client needs additional logic for this.
The text was updated successfully, but these errors were encountered:
How to use GitHub
Feature description
When we move some files/placeholders within the structure of the local sync folder, we might end up not being able to upload them to a new location on the server. The most recent case that I've encountered was with a user trying to move many files/folders from someone else's folder to the user's home folder. Since the user did not have enough space in the home folder on the server and received a lot of 507 errors, files were not uploaded to a new location on the server but stayed in a new location in the user's local folder.
We need to implement the roll-back mechanism so the file would get moved to its original location locally if the move has failed. The desktop client needs additional logic for this.
The text was updated successfully, but these errors were encountered: