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
Feature Request: only update daily notes on the one computer that is currently seeing activity, to avoid backend sync issues #43
Comments
could you elaborate a little? what are the conflicts? how/when exactly do they happen? could help me understand better :)
if you mean what i think you mean, this is not possible... all i can do is manipulate a file on your local computer the plugin is installed on |
syncthing synchronizes in the background and is typically able to merge conflicts automatically. Most conflicts are in the list of recently edited files at the bottom updated by this plugin, and they are conflicts for the daily log itself. So my theory is that the plugin is active on multiple computers, which then triggers creating a conflict file, and that conflict file then gets added to the daily log on either computer, causing a few repeats until one sync does automatically merge, at which the chain stops. |
do the conflict files follow a certain naming convention? i could add a feature to ignore files that match a certain regex pattern edit: googled it and it seems to be would love if you could confirm though :) |
If yes, I could make this a setting. just gotta create |
@thomasvs can you please give me an update on this? |
Closed due to inactivity |
I don't have any conflict files right now to compare it to, but the regex you propose looks correct to me. That may reduce issues with use on multiple computers when using SyncThing. |
Enabling this plugin on multiple computers that I sync with SyncThing, I notice it ends up creating a lot of conflicts. My guess is that's because the plugin is running on multiple computers, making changes to the daily notes on each of them independently, and making conflict resolution hard/impossible for the underlying sync mechanism.
I saw another issue that seemed similar on iCloud.
I think one way the issue can be avoided is for the plugin to be aware of the Obsidian process being actively used or not in some way, so that only one copy at any point is getting updates.
I don't know if obsidian exposes a useful signal of activity?
The text was updated successfully, but these errors were encountered: