SyncTrayzor
SyncTrayzor copied to clipboard
No way to dismiss "Following folder had sync problems" warning?
When trying to sync a folder, this warning popped up and was also resembled in the details of that folder. However, I then set up the .stignore
file and excluded all folders that had problems. The web view stopped showing any problems but the yellow warning bar (and the exclamation mark in the tray icon) didn't go away. Even restarting Syncthing didn't help. Only after exiting SyncTrayzor and starting it up again, the warning was gone.
this warning popped up and was also resembled in the details of that folder
Can you provide more details? What did it look like? Where did it display? Have you got a screenshot?
There are two yellow warnings that pop up at the top, one is part of SyncTrayzor and the other is part of Syncthing. Knowing which it is is critical to investigating this.
It displayed at the top of the SyncTrayzor window, right below the menu line. And I couldn't right-click the yellow bar. When right-clicking anywhere else, I get a menu with Cut, Copy, Paste. Also when restarting Syncthing from within SyncTrayzor, the web view vanished for a few seconds, but the yellow bar stayed. So to me this looks like it was part of SyncTrayzor.
I'm currently trying to provoke it again. Will post screenshots if it works.
EDIT: Of course, now it works without any errors. :disappointed:
Cool, and what did it say, exactly? It could have been one about conflicted files, or one about failed transfers.
I'm pretty sure it was about failed transfers as the log was full of something like:
.... file C:\....\xyz.tmp already exists
And the web gui showed something about it not being able to get the latest version of various files. But as I said: Clearing the log via the button, removing all offending paths via .stignore
and restarting syncthing from within SyncTrayzor didn't remove the warning even though the web gui didn't show any problem afterwards.
OK, I'll take a look into that, thanks.
This bar was introduced at a time when the notifications in Syncthing worked slightly differently (I don't think there was a way to clear them, for instance). There might not even have been a notification for this particular case. It might be that simply removing it is the right thing to do.
Looking at a bit more closely, this should disappear when all of the folder errors go away. I think I'd need to see a Debug log to find out what events exactly we received.
I just (during the last two days) experienced the same issue.
SyncTrayzor Version 1.1.24 SyncThing Version 1.4.0 On Windows 10 64bit
The issue was provoked by simultaneously having open the same XLSX file on two synced computers. On one computer the file was closed WITHOUT saving, on the other computer changes to the file were saved by the user. The XLSX tmp file confilicts were perfectly resolved by SyncThing, latest file version synced between all computers, tmp conflict files removed automatically.
However, SyncTrayzor continued showing the yellow exclamation mark triangle in the tray and the yellow error bar on top when SyncTrayzor window was open. The error displayed was: 'The following folder has failing file transfers: folder name' with the folder name displayed being the parent folder of the folder with the temporary conflict.
Folder and file seemed perfectly fine and sync seemed to work. Time did not resolve the error message. I eventually restarted SyncThing from within SyncTrayzor and the error reappeared.
Only when exiting and re-starting SyncTrayzor did the error message go away and all seems to be back to normal.
I thus suspect the wrong error message issue to be on the side of SyncTrayzor.
Thank you for the great tool, your efforts are highly appreciated!
+1 - only restarting SyncTrayzor removes the alert, which is pretty annoying, especially when there are no longer any sync errors but only the alert sticks.
Same here, I had issues with XLSX tmp files like @agsfbm6 , but the most persistent was the following one: Changing the case of an existing file (mv boing.SH boing.sh
) on a case-sensitive OS, and watch syncthing despair on Windows. Then update the file, so the error disappears from syncthing, but the error in Synctrayzor persists until forcible restarted.
Downloading.csv
says:
Date,Folder,Path,Type,Action,Error
2020-08-12 20:00:23.7941,abcde-fghij,Mail\boing.sh,File,Update,file modified but not rescanned; will try again later
2020-08-12 20:00:23.7941,abcde-fghij,Mail\boing.sh,File,Update,file modified but not rescanned; will try again later
2020-08-12 20:00:23.8101,abcde-fghij,Mail\boing.sh,File,Metadata,
At the same time the Synctrazor.log
says:
2020-08-12 20:00:23.7941 #19860 [Warn] SyncTrayzor.Syncthing.Folders.FolderStateTransformer: Unknown folder sync state sync-preparing. Defaulting to Idle
2020-08-12 20:00:23.8101 #19860 [Warn] SyncTrayzor.Syncthing.Folders.FolderStateTransformer: Unknown folder sync state sync-preparing. Defaulting to Idle
2020-08-12 20:00:23.8101 #19860 [Warn] SyncTrayzor.Syncthing.Folders.FolderStateTransformer: Unknown folder sync state scan-waiting. Defaulting to Idle
2020-08-12 20:00:23.8101 #19860 [Warn] SyncTrayzor.Syncthing.Folders.FolderStateTransformer: Unknown folder sync state scan-waiting. Defaulting to Idle
2020-08-12 20:00:23.8101 #19860 [Warn] SyncTrayzor.Syncthing.Folders.FolderStateTransformer: Unknown folder sync state sync-waiting. Defaulting to Idle
2020-08-12 20:00:23.8101 #19860 [Warn] SyncTrayzor.Syncthing.Folders.FolderStateTransformer: Unknown folder sync state sync-preparing. Defaulting to Idle
2020-08-12 20:00:23.8101 #19860 [Warn] SyncTrayzor.Syncthing.Folders.FolderStateTransformer: Unknown folder sync state sync-waiting. Defaulting to Idle
2020-08-12 20:00:23.8101 #19860 [Warn] SyncTrayzor.Syncthing.Folders.FolderStateTransformer: Unknown folder sync state sync-preparing. Defaulting to Idle
I think this issue appears when you resolve conflict on another device I had an error that "folders on windows can't end with period" so Syncthing couldn't sync a folder, and after I deleted that folder from my phone, I got the same issue: that yellow bar just doesn't want to go away, even though there is no sync problems and everything is working fine
I get the yellow warning that can't be dismissed as well on Synctrayzor. Not a huge problem, just annoying.
I think this issue appears when you resolve conflict on another device I had an error that "folders on windows can't end with period" so Syncthing couldn't sync a folder, and after I deleted that folder from my phone, I got the same issue: that yellow bar just doesn't want to go away, even though there is no sync problems and everything is working fine
I just experienced the same issue! I had a warning about a folder : sync issues because of the conflicts with the naming ("?" caracter that Windows doesn't appreciate. After correcting the issue on the other computer, there were no issues anymore in the console but the yellow warning bar was still there. I had to restart SyncTraizor to dismiss this bar.
The trick seems to be to restart SyncTrazor, which is totally different from restarting SyncThing itself (which did not help). Right click -> Close, on the system process in the bottom right of the Taskbar solved the problem for me :+1:
Still running into this issue, version 1.1.29
Is this project dead? Haven't seen any activity in over a year.
Still present, still annoying. One way to mitigate is to outright disable "Alert of failed transfers". It is separate from alerts for conflicting files, so at least these will still appear as normal.
I just ran into this after updating a binary from another device when it was in use on my desktop. I exited the running program so Syncthing could update the file, but now on my desktop even though Syncthing shows all Up to Date, SyncTrayzor continues to show the yellow banner.
SyncTrayzor's Conflict Resolver shows "No conflicts found. Good job!"
SyncTrayzor v1.1.29, Syncthing v1.22.0
FYI, this is still an issue. After cleaning out what was causing the failure, restarting ST, and even rebooting PC, the error ribbon remains.
Currently having the same issue.
Clearly this project is dead and abandoned.