Simon Frei

@tomasz1986 > On a side note, strictly speaking, following Bootstrap, the line below should use `767px` instead of `768px`, but I'm not sure if the fix fits into this PR?...

Policybot thinks no contributor has approved - somehow it doesn't see Jakobs approval?! Anyway, I am force merging.

I think it isn't what the original issue was about, but I can see the merit of some kind of status indication during the walking phase in very slow setups....

That part isn't my problem. In the scanning implementation the only thing that makes sense (no more resources, reasonably easy) is the same system as with the current hashing progress...

What I was thinking about on the non-GUI side is pretty simple: https://github.com/imsodin/syncthing/commit/619ba6b3cb7cda1f3a394b0bbd3cdc39884877ff If anyone wants to do the GUI part, feel free to use that if it suits your...

It's not super easy, as it involves model-folder interactions and handling config changes. As in currently folders are indiscriminately restarted when their config changes, which would have to be changed...

I thought the restart annotations are only for full Syncthing restarts. If it is meant to apply to folder restarts, that's not only not working, but also not fully implemented:...

I'd check the DB for conflict files when this API is called. Then there's no need to have the overhead of tracking and keeping conflict files in memory. Also probably...

Though I haven't actually read the ticket - if you plan on constantly showing that in the UI, repeatedly walking the DB isn't an option, too expensive. If it were...

So a counter and a db walk to find the conflicts when the user requests that information seems like a reasonable way to go.