nextcloud / nextcloud/notes

Data loss due to unreliable sync and lots of missing version change history

Open
#1,207 12 comments 4 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

bug need to reproduce
Dominant language
JavaScript
Stars
738
Forks
162
Avg merge
6h 2m
Merged PRs (30d)
35

Description

I have now lost multiple notes due to sync between either a desktop or android tablet not quite working right, and the version history being barely any entries. I just wrote like 10 questions for a job interview I'm about to do that should have been sync'd back to the server multiple times, but by the time I got back to my desktop, I lost half of these questions because the desktop version got synced overtop of the tablet work, and NONE of the "version history" versions for the file itself (when going into the Files function) has ANY of the data lost.

And this ISN'T the first time this has happened!

A sync ecosystem like this cannot have this much data loss, and frankly if it keeps up being this egregiously unreliable, I'm going to just stop using Notes through nextCloud completely.

Data loss for things like this cannot be acceptable, especially overwritting back onto the tablet like I've described. I could understand losing maybe a few characters or something, but ugh.

Anyways, this is clearly a bug composing of multiple aspects, including the incomplete Version Control aspect.

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

No files, tests, or entry points are named. Start by reproducing sync between a desktop and Android tablet while checking the file's version history. Done means edits are not overwritten or lost during sync and the recovered versions contain the missing changes.

Written by the indexing model from the issue text.

Assessment

Tech stack
javascript
Domain
data, distributed-systems
Issue type
Bug
Difficulty
5/5
Estimated time
Over a week
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
20/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.