How do I use the Plugin and settings (beta)

[Vyeche]

Hi,

I love the Plugin and setting sync! Great feature.

Not sure how to use it. I read through the document, but something is missing where I do not see the other device.

• https://github.com/vrtmrz/obsidian-livesync/blob/main/docs/settings.md#plugins-and-settings-beta

I'm curious about how to use the plugin and settings sync. Not sure why replication failed. It doesn't give any more details. I do see some settings for hidden files. Not sure if those need to be enabled while using the beta plugin sync.

Nothing appears on either side of my different device. I have a name given to each device. "Chromebook" and "desktop."

----remote config----
Requesting information to the remote CouchDB has failed. If you are using
IBM Cloudant is the normal behavior.

I noticed that the vault name is not being saved into the data.json

[Vyeche]

Output from make report.

----remote config----
Requesting information to the remote CouchDB has been failed. If you are using
IBM Cloudant, it is the normal behaviour.

---- Plug-in config ---
couchDB_URI: cloudant
couchDB_USER: 𝑅𝐸𝐷𝐴𝐶𝑇𝐸𝐷
couchDB_PASSWORD: 𝑅𝐸𝐷𝐴𝐶𝑇𝐸𝐷
couchDB_DBNAME: 𝑅𝐸𝐷𝐴𝐶𝑇𝐸𝐷
liveSync: false
syncOnSave: false
syncOnStart: true
savingDelay: 200
lessInformationInLog: true
gcDelay: 0
versionUpFlash: ""
minimumChunkSize: 20
longLineThreshold: 250
showVerboseLog: true
suspendFileWatching: false
trashInsteadDelete: true
periodicReplication: true
periodicReplicationInterval: 60
syncOnFileOpen: true
encrypt: false
passphrase: 𝑅𝐸𝐷𝐴𝐶𝑇𝐸𝐷
workingEncrypt: false
workingPassphrase: 𝑅𝐸𝐷𝐴𝐶𝑇𝐸𝐷
doNotDeleteFolder: false
resolveConflictsByNewerFile: false
batchSave: true
deviceAndVaultName: ""
usePluginSettings: false
showOwnPlugins: false
showStatusOnEditor: true
usePluginSync: false
autoSweepPlugins: false
autoSweepPluginsPeriodic: false
notifyPluginOrSettingUpdated: false
checkIntegrityOnSave: false
batch_size: 250
batches_limit: 40
useHistory: true
disableRequestURI: true
skipOlderFilesOnSync: true
checkConflictOnlyOnOpen: true
syncInternalFiles: false
syncInternalFilesBeforeReplication: false
syncInternalFilesIgnorePatterns: \/node_modules\/, \/\.git\/, \/obsidian-livesync\/
syncInternalFilesInterval: 60
additionalSuffixOfDatabaseName: ""
ignoreVersionCheck: false
lastReadUpdates: 16
deleteMetadataOfDeletedFiles: false
syncIgnoreRegEx: ""
syncOnlyRegEx: ""
customChunkSize: 0
readChunksOnline: true
watchInternalFileChanges: true
automaticallyDeleteMetadataOfDeletedFiles: 0

[Vyeche]

@vrtmrz

The data.json file gets changed for plugins. I understand what you mean. So that's why the message comes. Right?

The issue I noticed is that the plugins turn off.

[Vyeche]

I need to spend some more time understanding the terms. In the mean time I got an idea.

Is it possible for the chunk and batch size to be adaptive based on your table?

Say for example when it fails it adjusts a few times to correct itself until it files success and then sets up to the correct working settings. That way the user doesn't need to fiddle with that area.

Perhaps you can add a checkbox for adaptive chunking and batching.

What do you think? @vrtmrz

[vrtmrz]

Thank you for the screenshot!
Maybe a feature like Reload specific plugins automaticallywill be useful, if these plugins can be reloaded immediately and no side effects (LiveSync and TagFolder are slow-stater so they will be treated annually )

Is it possible for the chunk and batch size to be adaptive based on your table?

Completely as you said is right!
Already LiveSync (might) detects that payload size is exceeded, and (in design) it reduces batch limit to adopt automatically. But I split them, so we have to investigate more.

[Vyeche]

I noticed that even after I adjust the numbers, it will continue to fail seems tricky to figure out on my own. So we need some algorithms to keep trying. @vrtmrz

[vrtmrz]

Thank you so much for your cooperation May I see a screenshot of the network pane?
I want to know what URI makes this issue.

[Vyeche]

After removing the plugin something odd happened.
document_too_large:i:.obsidian/plugins/obsidian-admonition/main.js
Installing the app gets rid of the error.
Adjusting the batch size removed the error afterword.

[Vyeche]

The notification for the plugin gets too much.
Perhaps a way to toggle it off.

[Vyeche]

I see some 413 errors, but nothing interesting on network @vrtmrz
I noticed 'replication failure' when I had multiple devices syncing.

What's worse is that it broke the live sync (not plugin sync if they are different), or at least I noticed that my files look older than my other device files.

[Vyeche]

@vrtmrz I thought, what if the plugins had a single point of truth, let's say, my home desktop? Every time I update that area, my other devices will get the update instead of any device changing. I don't see myself adjusting my plugins as much as much notes. Perhaps that will remove these sync issues?

[vrtmrz]

Disabling the notification

It will be implemented soon! (Sorry, I will usually be a good dad on holidays). In that case, Just ignoring or automatically reloading should be configured.
However, perhaps we can avoid them by skipping data.json in synchronisation.

But sorry for breaking synchronisations. There must be some deeper problems. I'd love to thank you once again.
If file contents are the same, they will not be overwritten, so perhaps their timestamps look miss matched.

The 413 in the screenshot is apparently not in the list above. Which request was it?
This is a totally different solution, but what if I disable Read chunks online?

I thought, what if the plugins had a single point of truth,

Oh! This is the functionality that hidden file sync lacks and Plugins and their settings have.

I thought that almost everything can be solved by Sync hidden file. But these use-cases might be useful.
Still need some fixes, but it will not be obsoleted now. Thank you for your patience and for pointing me out!

[Vyeche]

@vrtmrz

That's great; thank you for the reply!

I will pause using the plugin sync; it is hard to use my vault productively. I will wait for some new updates to test later. I am looking forward to new updates.

Sorry for bugging you.

[vrtmrz]

Before fixing the plugin and settings, I fixed the feature which adjusts the batch limit automatically.
(Maybe it also fixes the plugin and settings.)

If some of the chunks are still big, we have to rebuild the database again. But it is also be detected.

It would be great if you could update it and give it a try.

[Vyeche]

Okay, I'll plan something maybe during the week or next because it was hard to stay productive while troubleshooting the plugins.

@vrtmrz
Is it possible for you can create another IBM test account, so I can quickly make a new vault and try it during the week?

[vrtmrz]

Thank you so much! I also think so, I really appreciate your significant contributions every time!

Is it possible for you can create another IBM test account, so I can quickly make a new vault and try it during the week?

I'm really sorry for telling you this, but I also could not make another Cloudant account. We can use different database names in the same Cloudant instance to split the influence. Could this help us?

Or fly.io could be very easy to set up and initialise.
Now it doesn't require installing clients locally. (I have found out the way to setting CouchDB up from google Colab)

[GSanrio]

In the new version of the plugin, there is no longer an item for selecting plugin synchronization in the custom settings. How should I set it up?