[tahoe-lafs-trac-stream] [Tahoe-LAFS] #2606: Magic Folder: account properly for NFC normalization

[Tahoe-LAFS]

#2606: Magic Folder: account properly for NFC normalization
-------------------------------------------------+-------------------------
 Reporter:  daira                                |          Owner:  daira
     Type:  defect                               |         Status:  new
 Priority:  normal                               |      Milestone:
Component:  code-frontend-magic-folder           |  undecided
 Keywords:  magic-folder reliability unicode     |        Version:  1.10.2
  nfc                                            |  Launchpad Bug:
-------------------------------------------------+-------------------------
 Tahoe-LAFS maps filenames to their NFC-normalized form. When a local path
 relative to the magic folder directory is not NFC, the corresponding
 encoded filename in the client's DMD will still be mapped to NFC. Then
 when the client reads its own DMD at start-up, it may be confused by the
 decoded path not matching the local db entry.

 This should probably be fixed by mapping the db paths to NFC both on
 creation and lookup.

 Note that the issue here isn't the fact that there can be distinct paths
 with the same NFC normalization (which can be expected to be a rare case);
 it's that the db may fail to do its job across restarts for filenames that
 are not NFC-normalized.

--
Ticket URL: <https://tahoe-lafs.org/trac/tahoe-lafs/ticket/2606>
Tahoe-LAFS <https://Tahoe-LAFS.org>
secure decentralized storage