CORS message and Conflicts & IBM Cloudant

[Vyeche]

Hi,

While using the live sync, I noticed that over time I build up conflicts or the false positive CORS message. I’ve seen that message before in .NET core and ASP.NET while using a C# API I built unrelated to IBM. My experience is that it’s usually a 500 error on the back end. Rebuilding and restarting doesn’t always fix the CORS issue while using multiple devices while batch sync is enabled.

The issues come more frequently when I rename and move files in Obsidian.

I’ve logged into IBM Cloud and I noticed conflicts are building up, but I don’t know the API so I can’t fix it.

Is there a way to view and fix the conflicts without going through the log? Is there an option to save the log? I checked out the menu for conflicts on the live sync plugin, but it always shows nothing. However, the log is showing issues.

The do not delete empty folder is not being respected even though its set to false. Something is conflicting.
https://github.com/vrtmrz/obsidian-livesync/blob/main/docs/settings.md#do-not-delete-empty-folder

Thanks & kind regards,
Vye

[vrtmrz]

Hi! thank you for opening this discussion!

I wonder what messages are shown, but in conflicts, the remote conflicts are also local conflicts. So we can resolve them by Pick a file to resolve conflict. (If it shows nothing, we don't have to resolve them)

Is there an option to save the log?

Unfortunately not. But it might help us. I will implement it.

[vrtmrz]

I have found several cases that LiveSync detects as CORS.
If there is an error, the error message will be detected as an illegal Cross-origin request.
Could you please click the red errored line and see the Response pane? Probaly, there is more information. (This message will not reach Obsidian and LiveSync, because of security reasons.)
I will be able to investigate it more with the message, if the message is not that having exceeded your quota. I also have reached it several times...

Edited: Sorry, this cannot be shown. and now reproduced.

[vrtmrz]

Is 429 shown anywhere? This means that we accessed the remote database too frequently. I didn't realised but as you said, perhaps we cannot use Read chunks online practically in the initial replication.
(or we have to delay the request file by file).

I will improve the doc.

But, if you have some other status codes, please let me know.

P.S. Once our synchronisation has been stable, we should be able to use Read chunks online. (That in my case)

[Vyeche]

214 requests came in and several show as 429.
Console is reporting 36 console CORS, setting console to blocked I see 18 in blocked requests. It doesn't seem to match the CORS.

[vrtmrz]

Thank you for your investigation! I am relieved that it was exactly as I thought.
It is not good for Cloudant. It also will be a performance issue in general cases.
It has been fixed in 0.15.9.

[Vyeche]

That’s great, i will try it out.