Skip to content
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

Wrong notification when a placeholder is renamed #7327

Open
HanaGemela opened this issue Jul 18, 2019 · 3 comments
Open

Wrong notification when a placeholder is renamed #7327

HanaGemela opened this issue Jul 18, 2019 · 3 comments
Assignees
Labels
feature:vfs native virtual files and placeholder implementation p3-medium Normal priority type:bug
Milestone

Comments

@HanaGemela
Copy link
Contributor

Client: 2.6.0alpha2 (build 12128)
macOS: 10.14.5
Server:10.2.1. (stable)

Steps to recreate:

  1. Rename a file
  2. Sync the file e.g. in different Account tab or on another machine that has VFS on so that the placeholder will be renamed

Actual result: User receives a notification that the old file has been removed and a new file has been added
Expected result: User receives a notification that the file has been renamed

@HanaGemela HanaGemela added type:bug p3-medium Normal priority feature:vfs native virtual files and placeholder implementation labels Jul 18, 2019
@HanaGemela HanaGemela added this to the 2.6.1 milestone Jul 18, 2019
@ogoffart
Copy link
Contributor

It worked for me: the notification states that the file was moved.

@ogoffart ogoffart added the ReadyToTest QA, please validate the fix/enhancement label Oct 16, 2019
@HanaGemela
Copy link
Contributor Author

Still broken on 2.6.1-daily20191127 (build 12791), macOS 10.15.1 when syncing rename from Windows to Mac.
If the rename is synced from Mac to Windows, there is no notification at all on Windows.

@HanaGemela HanaGemela removed the ReadyToTest QA, please validate the fix/enhancement label Nov 29, 2019
@michaelstingl michaelstingl modified the milestones: 2.6.1, 2.6.2 Dec 2, 2019
@TheOneRing
Copy link
Contributor

I think that issue sums up the current issue with the placeholder files.
We can't detect a move with placeholder files.

This lies in the nature of the current implementation.
Placeholder files hold no data, only the file name provides data.
If we would write the original file path and hash to the file, we could detect a move when encountering placeholder in a new location....

@ogoffart what do you think?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
feature:vfs native virtual files and placeholder implementation p3-medium Normal priority type:bug
Projects
None yet
Development

No branches or pull requests

4 participants