{"version":"2.1.282","anchor":"directory-sync-snapshot-tampered-object-and-legacy-tree-ref","canonical_anchor":"directory-sync-snapshot-tampered-object-and-legacy-tree-ref","heading":"Cloud file sync refuses damaged git data and handles unusual file names","tier":"notice","area":"File Sync","url":"https:\/\/changelogs.core-directive.com\/v\/2.1.282\/e\/directory-sync-snapshot-tampered-object-and-legacy-tree-ref","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.282","markdown":"### Cloud file sync refuses damaged git data and handles unusual file names\n\nDirectory sync now refuses snapshots with tampered or old-format git data by name and copes better with file names that are not valid UTF-8\n\n**What**\n\nDirectory sync keeps your local folder and a cloud session in step by taking snapshots of your project with git, the version control tool. Several things about building those snapshots have changed:\n\n- Git data that fails an integrity check is now refused as \"tampered\", instead of being reported as a general git error.\n\n- Malformed git trees (the records of folder contents) are refused with a new \"legacy_tree\" reason.\n\n- Each snapshot is read back and checked against what it should contain.\n\n- Staged file names that are not valid UTF-8 text are carried through.\n\n- If something is staged where a folder holding such a name stood, the snapshot is refused, and you are told to commit that change first and then send again.\n\n- The snapshot now carries a list of the changes found in your staged files and your working folder.\n\n**Why**\n\nSync is harder to fool with damaged or forged git data, and it copes better with file names in unusual encodings.\n\n- Area: File Sync\n- Tier: You'll notice\n- Useful: 1\/5\n- Signal: 1\/5"}