Scram Enabled warning on plugin enabled

[yegorsw]

I mistakenly clicked "Flag and Restart" and was getting some warning message. So I removed the entire plugin and reinstalled it from scratch, but I get this warning as soon as I enable it:

Self-hosted LiveSync has been configured to ignore some events. Is this intentional for you?

Type    Status  Note
Storage Events  suspended   Every modification will be ignored
Database Events active  Every synchronised change will be postponed
Do you want to resume them and restart Obsidian?

Clicking "resume and restart" reboots the app, and the warning is displayed again immediately.

Here is the entire log from app start:

app.js:1 Obsidian Developer Console
plugin:table-editor-obsidian:183 loading markdown-table-editor plugin
plugin:obsidian-icon-folder:6445 loading iconize
plugin:obsidian-livesync:6 Yegor-ls-226a8e2c0f7f00be:10/11/2024, 18:53:35->[ModuleLiveSyncMain]  loading plugin
plugin:obsidian-livesync:6 Yegor-ls-226a8e2c0f7f00be:10/11/2024, 18:53:35->[ModuleLiveSyncMain]  Self-hosted LiveSync v0.24.1 0.24.1
plugin:obsidian-livesync:6 Yegor-ls-226a8e2c0f7f00be:10/11/2024, 18:53:35->[HiddenFileSync]  Hidden file will skip 0 files
plugin:obsidian-livesync:6 Yegor-ls-226a8e2c0f7f00be:10/11/2024, 18:53:35->[ModuleLocalDatabaseObsidian]  Waiting for ready...
plugin:obsidian-livesync:6 Yegor-ls-226a8e2c0f7f00be:10/11/2024, 18:53:35->Opening Database...
plugin:obsidian-livesync:6 Yegor-ls-226a8e2c0f7f00be:10/11/2024, 18:53:35->Database is now ready.
plugin:omnisearch:107 Loading index from cache: 75.84521484375 ms
plugin:obsidian-livesync:6 Yegor-ls-226a8e2c0f7f00be:10/11/2024, 18:53:35->[HiddenFileSync]  Hidden file will skip 0 files
plugin:obsidian-livesync:6 Yegor-ls-226a8e2c0f7f00be:10/11/2024, 18:53:35->The red flag is raised! The whole initialize steps are skipped, and any file changes are not captured.
plugin:omnisearch:107 Indexing total time: 175.711181640625 ms

[vrtmrz]

Thank you for your question! This is designed behaviour, but it is misleading. That disabled event is caused by a flag file. So, we have to delete the redflag.md on our vault. (Possibly, the flag file's notification is also required).

Please try answering as Keep this plug-in suspended, delete the redflag.md, and restart Obsidian. We will be asked again, this time, we can answer resume and restart and it will not be reverted.

[yegorsw]

Oh, thank you! I searched the repo and documentation for flag, scram, anything like that but couldn't find it. I should have checked the code!