I just realized that some of my ignore patterns don’t work the way they used to and, after a bit of research, I found that this MR might be the culprit.
My use case is exactly the one described here and I solved it exactly this way. Typically I want to backup some apps settings and other files stored in my home folder and in
~/Library/Application Support, so I created a Syncthing folder with the path set to my home folder and a
.stignore file that looked like this :
!/Library/Application Support/Sublime Text 3/Packages/User /Library/Application Support/Sublime Text 3/Packages/ !/Library/Application Support/Sublime Text 3/Packages /Library/Application Support/Sublime Text 3/ !/Library/Application Support/Sublime Text 3 /Library/Application Support/ !/Library/Application Support /Library/ !/Library !/.ssh !/.zshrc !/.gitignore !/.vimrc !/.gitconfig **
And it worked fine.
Now I understand that this MR intended to make writing such ignore patterns easier, and from what I can see it works (yeah !), since I’m now able to shrink my patterns to just :
!/Library/Application Support/Sublime Text 3/Packages/User !/.ssh !/.zshrc !/.gitignore !/.vimrc !/.gitconfig **
However, I feel that what @imsodin foresaw (i.e. : “Potentially a lot more data to traverse/stat”) is a thing, especially in my case since an initial scan of my folder (I reset it with the API between my pattern tweaks for accurate results) takes forever now (compared to instants before the update), with an endless load of these lines in the scanner logs :
2019-01-28 23:05:22 ignored (patterns): <some ignored path in my ~ directory>
I believe the scanner is now traversing my whole home folder, despite the
** in my patterns and I can’t figure out how to prevent this behavior.
Is there something I’m missing ? How can we efficiently treat this kind of use case after this update ?
Edit : I actually noticed the problem while trying to fix another issue by upgrading to
1.0.1-rc.2, just so you know what version I’m using right now.