Opened at 2015-10-27T01:32:35Z

Closed at 2015-11-04T01:22:31Z

Last modified at 2016-07-21T21:32:36Z

#2553 closed defect (fixed)

Magic Folder: a client should not read or download from its own DMD after start-up

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

Description (last modified by daira)

A Magic Folder client should not read its own DMD, except on the start-up scan before it writes anything to that DMD.

See 1105#comment:8. Also, this will cause spurious conflicts and inefficiency.

Change History (4)

comment:1 Changed at 2015-10-27T01:34:12Z by daira

  • Description modified (diff)

comment:2 Changed at 2015-10-30T09:14:30Z by daira

  • Description modified (diff)
  • Summary changed from Magic Folder: check that the implementation avoids #1105 to Magic Folder: a client should not read or download from its own DMD after start-up

comment:3 Changed at 2015-11-04T01:22:31Z by daira

  • Resolution set to fixed
  • Status changed from new to closed

The start-up scan is #2449, and the rest of this ticket is implemented on the 2553.do-not-read-from-own-dmd.3 branch.

comment:4 Changed at 2016-07-21T21:32:36Z by Brian Warner <warner@…>

In 84af199/trunk:

WIP: exclude own dirnode from scan. This is not quite right; we shouldn't exclude it on startup. refs #2553

Signed-off-by: Daira Hopwood <daira@…>

Note: See TracTickets for help on using tickets.