{"action":"created","issue":{"url":"https://api.github.com/repos/cryptomator/cryptomator/issues/304","repository_url":"https://api.github.com/repos/cryptomator/cryptomator","labels_url":"https://api.github.com/repos/cryptomator/cryptomator/issues/304/labels{/name}","comments_url":"https://api.github.com/repos/cryptomator/cryptomator/issues/304/comments","events_url":"https://api.github.com/repos/cryptomator/cryptomator/issues/304/events","html_url":"https://github.com/cryptomator/cryptomator/issues/304","id":164539187,"number":304,"title":"Issue with updating to new vault format & MegaSync","user":{"login":"RiseT","id":12624674,"avatar_url":"https://avatars.githubusercontent.com/u/12624674?v=3","gravatar_id":"","url":"https://api.github.com/users/RiseT","html_url":"https://github.com/RiseT","followers_url":"https://api.github.com/users/RiseT/followers","following_url":"https://api.github.com/users/RiseT/following{/other_user}","gists_url":"https://api.github.com/users/RiseT/gists{/gist_id}","starred_url":"https://api.github.com/users/RiseT/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/RiseT/subscriptions","organizations_url":"https://api.github.com/users/RiseT/orgs","repos_url":"https://api.github.com/users/RiseT/repos","events_url":"https://api.github.com/users/RiseT/events{/privacy}","received_events_url":"https://api.github.com/users/RiseT/received_events","type":"User","site_admin":false},"labels":[{"url":"https://api.github.com/repos/cryptomator/cryptomator/labels/type:dev-task","name":"type:dev-task","color":"fbca04"},{"url":"https://api.github.com/repos/cryptomator/cryptomator/labels/type:upstream-bug","name":"type:upstream-bug","color":"f9d0c4"}],"state":"closed","locked":false,"assignee":null,"assignees":[],"milestone":{"url":"https://api.github.com/repos/cryptomator/cryptomator/milestones/21","html_url":"https://github.com/cryptomator/cryptomator/milestones/1.1.2","labels_url":"https://api.github.com/repos/cryptomator/cryptomator/milestones/21/labels","id":1873519,"number":21,"title":"1.1.2","description":"","creator":{"login":"tobihagemann","id":2924160,"avatar_url":"https://avatars.githubusercontent.com/u/2924160?v=3","gravatar_id":"","url":"https://api.github.com/users/tobihagemann","html_url":"https://github.com/tobihagemann","followers_url":"https://api.github.com/users/tobihagemann/followers","following_url":"https://api.github.com/users/tobihagemann/following{/other_user}","gists_url":"https://api.github.com/users/tobihagemann/gists{/gist_id}","starred_url":"https://api.github.com/users/tobihagemann/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/tobihagemann/subscriptions","organizations_url":"https://api.github.com/users/tobihagemann/orgs","repos_url":"https://api.github.com/users/tobihagemann/repos","events_url":"https://api.github.com/users/tobihagemann/events{/privacy}","received_events_url":"https://api.github.com/users/tobihagemann/received_events","type":"User","site_admin":false},"open_issues":0,"closed_issues":1,"state":"closed","created_at":"2016-07-09T11:48:05Z","updated_at":"2016-07-09T12:15:23Z","due_on":null,"closed_at":"2016-07-09T12:15:23Z"},"comments":16,"created_at":"2016-07-08T14:10:29Z","updated_at":"2016-07-09T15:08:59Z","closed_at":"2016-07-09T12:15:12Z","body":"### Basic Info\r\n\r\n- I'm running Cryptomator on: [Windows 10 (Computer A), Windows 7 (Computer B)]\r\n- I'm using Cryptomator in version: [1.1.1, 64 bit]\r\n\r\n### Description\r\n**Setup:**\r\n\r\n2 computers which both synchronize a Cryptomator vault via the MegaSync client\r\n\r\n**Steps:**\r\n\r\n1. Made sure that both computers are in sync\r\n2. Exited MegaSync client on Computer B in order to prevent interfering synching\r\n3. Started Cryptomator on Computer A and updated vault to new vault format\r\n4. Waited for MegaSync client on Computer A to finish uploading the updated vault files (new vault format)\r\n5. Made MegaSync client on Computer A do a rescan in order to make 100% sure that the vault files are uploaded completely and correctly. Everything fine.\r\n6. Launched MegaSync client on Computer B in order to download the new vault files\r\n\r\n**Result:**\r\n\r\n* Computer B is downloading the new vault files (with the prepended \"0\"), BUT at the same time, uploading the old vault files (with the appended \"_\").\r\n* Computer A is downloading the old vault files\r\n\r\n**Final Result:**\r\n\r\nThe vault folders on both computers (and in the cloud) contain both versions of the vault files\r\n\r\nThis seems like an issue with MegaSync, but any thoughts?\r\n\r\n### Log File (optional)\r\nNone"},"comment":{"url":"https://api.github.com/repos/cryptomator/cryptomator/issues/comments/231538951","html_url":"https://github.com/cryptomator/cryptomator/issues/304#issuecomment-231538951","issue_url":"https://api.github.com/repos/cryptomator/cryptomator/issues/304","id":231538951,"user":{"login":"tobihagemann","id":2924160,"avatar_url":"https://avatars.githubusercontent.com/u/2924160?v=3","gravatar_id":"","url":"https://api.github.com/users/tobihagemann","html_url":"https://github.com/tobihagemann","followers_url":"https://api.github.com/users/tobihagemann/followers","following_url":"https://api.github.com/users/tobihagemann/following{/other_user}","gists_url":"https://api.github.com/users/tobihagemann/gists{/gist_id}","starred_url":"https://api.github.com/users/tobihagemann/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/tobihagemann/subscriptions","organizations_url":"https://api.github.com/users/tobihagemann/orgs","repos_url":"https://api.github.com/users/tobihagemann/repos","events_url":"https://api.github.com/users/tobihagemann/events{/privacy}","received_events_url":"https://api.github.com/users/tobihagemann/received_events","type":"User","site_admin":false},"created_at":"2016-07-09T15:08:59Z","updated_at":"2016-07-09T15:08:59Z","body":"Interesting idea. I'll spin it a little further: How about introducing more specific versions instead of relying only on a global vault version.\r\n\r\nWe could do something like:\r\n- File's filename version\r\n- Directory's filename version\r\n- File content version\r\n\r\nE.g.\r\n- Vault version 3 supports file's filename version 1, directory's filename version 1, and file content version 1\r\n- Vault version 4 supports file's filename version 1, directory's filename version 2, and file content version 1\r\n\r\nThere are two reasons, why I'm thinking of this solution:\r\n1. Obviously due to this issue that sync conflicts can mix up files from multiple vault versions, even though a vault has been successfully migrated.\r\n2. If we're introducing new vault versions, we don't have to change EVERY single file, just the ones that are affected. E.g. if we would introduce vault version 5, we wouldn't have to rename every single file (or even read/write every single file, if we'd store the vault version inside the file content).\r\n\r\nI think we should discuss this in a separate issue. Maybe this whole crazy versioning isn't necessary and we still could introduce something like a \"Integrity Check\" button as you've suggested. Some kind of Troubleshooting / Clean Up / Janitor process.\r\n\r\nI'd like to hear some thoughts from the other @cryptomator/collaborators, before creating a new issue."}}
{"actor":{"display_login":"tobihagemann"}}