-
-
Notifications
You must be signed in to change notification settings - Fork 303
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
[Bug]: Namespace issues causing files to appear as empty in Android potentially causing dataloss #794
Comments
In here, this is the termux output(similar results when using adb) The interesting thing is that this does not occur to all files, but rather, it occurs randomly(and the larger the commit history, the more likely it'd happen) TL;DR: The android system sees the file as empty(and expectedly, git), but using cat proves otherwise. |
Okay, after thinking about it for a while, perhaps it's being caused by multiple writes to the same file when checking out from a large commit history size to the current file. Maybe there are multiple writes that are happening to the same file which causes a race condition somehow? |
@Vinzent03 Hey, I am not sure whether if this is considered to be an Obsidian plugin issue or if it's an Obsidian issue with their Adapter and Vault APIs. |
Describe the bug
When using Obsidian Git plugin on Android, certain files exhibit a filesystem metadata inconsistency after performing git operations across large commit differences.
Specific symptoms:
ls -la
orfile
commands (showing 0 bytes)cat
command(using termux/adb)Relevant errors
No direct error messages are shown, but filesystem inspection reveals:
Steps to reproduce
Expected Behavior
ls -la
should match the actual content sizeAdditional context
Operating system
Android
(Issue was reproduced on my Xiaomi Pad 6 and Samsung device)
Installation Method
None
Plugin version
2.27.0
The text was updated successfully, but these errors were encountered: