Thanks @WhiteNoise
Let’s assume you’re right, and this bug is caused by some other process on my system (I don’t edit my vault files in anything else but Obsidian btw). Why would Obsidian blindly “accept” a change that zeroes out the file while it’s running?
Here’s a screenshot of snapshots for this file:
The red outline shows the 0 byte version captured at 3:28pm. According to my time tracking software, I had not touched Obsidian since 3:17pm:
When I last used it, I was editing that file, and I am certain that its contents were intact.
I have a backup script that backs up my entire vault to a timestamped tar.zst archive once per hour:
Here’s the run from 2:28pm:
And here’s the one from 3:28pm with the 0-byte:
So somewhere between 3:17 and 3:19, something ate my file. It’s interesting because there’s a snapshot in Obsidian from 3:19 that is 3.42kb, so the zeroing must have occurred either simultaneously with that or within seconds after it.
Again I am just looking for some kind of straw to grasp onto to try and figure out what’s going on here.
@rigmarole No I don’t use iCloud anymore and have not for many months (since around May 21st).
since the original top post, I’ve updated my Obsidian to the 0.13.19 installer version with no .asar patch.