Accidentally nesting a project inside of itself will break sync

Steps to reproduce

Hey! I set Obsidian up on my chromebook (as a flatpak) and got a subscription to sync. I was tinkering around with getting a vault that i started on iOS set up, and set up sync (and then re-setup sync) without realizing that i had nested a project inside itself.

Expected result

Obsidian should notice if a vault is nested inside itself, and should throw an error of some kind.

Actual result

Obsidian Sync happily started recursing and reifying all of the files in the nested project in the background. I didn’t realize anything was amiss until i noticed that my iOS Obsidian vault was no longer connecting & syncing. It wasn’t until i looked at the log that i noticed that sync was trying to push these gigantic file paths.

I ended up deleting the directory from my ChromeOS install, and it’s taken hours for sync to push all the deletes up, and then for them to sync back down to iOS.

Environment

  • Operating system:
  • Debug info:

Additional information

1 Like

Obsidian should notice if a vault is nested inside itself, and should throw an error of some kind.

I don’t consider this a bug. Please, Open a feature request.