Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Syncfile / Overwritten dataset after failed sync attempt #612

Closed
ximenabb opened this issue Oct 28, 2021 · 0 comments · Fixed by #624
Closed

Syncfile / Overwritten dataset after failed sync attempt #612

ximenabb opened this issue Oct 28, 2021 · 0 comments · Fixed by #624
Assignees
Labels

Comments

@ximenabb
Copy link

ximenabb commented Oct 28, 2021

Describe the bug
Failed attempt to sync is still overwriting the syncfile when it shouldn’t, causing data to be lost/manipulated.

How to reproduce

  1. On desktop, import custom config and record some data.
  2. Export data as a syncfile
  3. Clean up desktop so that you go back to default configuration
  4. Attempt to sync with syncfile created in (2). It should fail
  5. Import the same custom config used in (1)
  6. Repeat (4). This time it seems like it works (no errors are surfaced), but notice that no database entries are being synced. Only media is synced.
  7. If you look in the kappa.db folder, you’ll see media was successfully transferred over. You’ll also notice that the database file size has changed (probably decreased). Since syncfiles are two-way, step (6) essentially has removed the recorded database data from the syncfile, but the images remain. Those images will get ported over as you continue to use the same syncfile, accumulating “orphaned” images on the machine (i.e. images without associated db data)

Mapeo Version:

  • Desktop - v.5.4.0

Additional context

Video of the issue walkthrough - https://drive.google.com/drive/folders/1nXVOwdwtGdVkwADl2CXV7h1qTYph7gOg

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants