{"version":"2.1.281","anchor":"laptop-generation-sync-handles-non-utf-8-paths-byte-exactly","canonical_anchor":"laptop-generation-sync-handles-non-utf-8-paths-byte-exactly","heading":"Laptop-generation sync handles non-UTF-8 paths byte-exactly","tier":"notice","area":"Cloud Sync","url":"https:\/\/changelogs.core-directive.com\/v\/2.1.281\/e\/laptop-generation-sync-handles-non-utf-8-paths-byte-exactly","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.281","markdown":"### Laptop-generation sync handles non-UTF-8 paths byte-exactly\n\nLaptop-generation sync now handles file paths that are not valid UTF-8 byte for byte\n\n**Unclear.** The finding does not say what laptop-generation sync is or when a user would encounter it.\n\n**What**\n\nIn laptop-generation sync, moving files to the trash and updating the scratch index now carry each path's raw bytes (`pathBytes`) instead of text. File removals are also passed to git as raw bytes rather than joined strings, and the record of trash moves is rebuilt from a diff limited to the removed paths.\n\n**Why**\n\nFile names that are not valid UTF-8 text are no longer mangled, which could otherwise lead to the error \"could not account for the trash moves\".\n\n- Area: Cloud Sync\n- Tier: You'll notice\n- Useful: 1\/5\n- Signal: 1\/5"}