Magic Folder: scan remote Tahoe upload directory upon local file deletion #2452

New Issue

tahoe-lafs · 2015-06-15T16:49:03Z

dawuud commented

2015-06-15 16:49:03 +00:00

This is related to tickets #1710 and #2440.

Once we've confirmed that a file has disappeared locally but has a previous entry in our magic folder db, we must scan the parent DMD for remote changes to that file with a higher version number than our own, detect overwrites/conflicts etc.

This is related to tickets #1710 and #2440. Once we've confirmed that a file has disappeared locally but has a previous entry in our magic folder db, we must scan the parent DMD for remote changes to that file with a higher version number than our own, detect overwrites/conflicts etc.

tahoe-lafs added the

labels 2015-06-15 16:49:03 +00:00

tahoe-lafs added this to the undecided milestone 2015-06-15 16:49:03 +00:00

tahoe-lafs added

code-frontend-magic-folder

and removed

unknown

labels 2015-07-07 18:45:14 +00:00

dawuud commented

2015-08-28 12:50:22 +00:00

I believe we've implemented this feature... in at least this dev branch 2477.refactor-all-the-things.1
After review this ticket should be closed.

I believe we've implemented this feature... in at least this dev branch 2477.refactor-all-the-things.1 After review this ticket should be closed.

daira commented

2015-12-03 20:38:26 +00:00

I'm not sure whether or not this case is tested.

daira commented

2016-02-11 15:21:46 +00:00

This doesn't need to be a special case. We should probably test the case where there is a conflict between a deletion and another client's change, but this ticket can be closed.

tahoe-lafs added the

invalid

label 2016-02-11 15:21:46 +00:00

tahoe-lafs closed this issue

2016-02-11 15:21:46 +00:00

Sign in to join this conversation.