Jakob Borg
Jakob Borg
Confirmed by creating an unexpected folder: Tapping revert removes it (and count of folders is reduced, but unexpected items status remains): Pausing and resuming the folder resolves.
There's a design error in that the `locations` package is global state. This should be a variable that's passed around appropriately instead. I'll sort that out.
This is currently ill defined, I think we will not do it.
I think we have a good error message for that case?
You'll see the actual error on the "failed items" like in the gui on the receiving side. The sending side has no info at all and can't show an error....
Out of sync means "we need to sync this file", failed items means "we tried to sync it but failed", and it will show both with some timing aspects deciding...
The sending side does indicate errors in case *on the sending side*, but if the problem is on the receiving side it does not and cannot.
Is this all because Syncthing doesn't support natively running as a service, or is it because of the CLI nature of the binary (that it pops a console window)? Supporting...
I think the answer I was looking for then is "no, just being able to run as a service natively wouldn't help massively".