Opened at 2015-11-30T17:43:01Z

Closed at 2020-06-30T13:41:55Z

#2582 closed defect (somebody else's problem)

Magic Folder: improve conflict detection to handle more than 2 clients

Reported by: daira Owned by: daira
Priority: major Milestone: undecided
Component: code-frontend-magic-folder Version: 1.10.1
Keywords: magic-folder usability reliability Cc:
Launchpad Bug:

Description (last modified by exarkun)

​https://tahoe-lafs.org/pipermail/tahoe-dev/2015-November/009615.html ​https://tahoe-lafs.org/trac/tahoe-lafs/browser/trunk/docs/proposed/magic-folder/multi-party-conflict-detection.rst

Change History (5)

comment:1 Changed at 2015-12-01T15:47:36Z by daira

Suggested design criteria:

  1. If before every update of a local file F on client A, A has time to observe and download the most recent update of F (and its ancestor directories), then no updates will be treated as conflicts by any client.
  1. Stopping a client and restarting it should not make a difference in terms of eventual consistency.
  1. There should be a documented way to purge all versions of a given file. (This need not be straightforward, and will likely require garbage collection.)

comment:2 Changed at 2015-12-03T18:08:30Z by daira

  • Keywords blocks-magic-folder-merge added; magic-folder removed
  • Status changed from new to assigned

Assigning to me to write the design tradeoff doc.

comment:3 Changed at 2015-12-14T15:12:32Z by daira

  • Keywords magic-folder added; blocks-magic-folder-merge removed

comment:4 Changed at 2020-01-17T16:26:01Z by exarkun

  • Description modified (diff)

comment:5 Changed at 2020-06-30T13:41:55Z by exarkun

  • Resolution set to somebody else's problem
  • Status changed from assigned to closed

magic-folder has been split out into a separate project - ​https://github.com/leastauthority/magic-folder

Note: See TracTickets for help on using tickets.