lobisee.blogg.se

1. #Syncthing disable dewvice connection notifications how to
2. #Syncthing disable dewvice connection notifications update
3. #Syncthing disable dewvice connection notifications code
4. #Syncthing disable dewvice connection notifications download

Even if they are not, there might be a device D which you don’t even know that connects B and C. B is in sync, C is yet not, yet you don’t necessarily know if B and C are interconnected or not. No, there is no easy way to check if you are the only available device with the files, but in a decentralized system you can’t reliably tell that anyway.

#Syncthing disable dewvice connection notifications code

GUI code already does something like that, so that’s the best place to check. You’d have to wait for RemoteIndexUpdate, as that’s the only significance that remote side has received something, and then check completion for each folder/device. But likely this is not worth the implementation effort.įolderCompletion is local folder, so it has no significance of what you are trying to achieve. Still, it would be cool if one node could just ask the others whether they could get up-to-date “without me”. One can just invoke syncthingctl for the remote instance where the files are expected to be downloaded: syncthingctl wait-for-idle -timeout 1800000 -at-least 5000 -dir concerning-dir -url -api-key foo-bar & systemctl poweroff Either way, I’d create a PR for making the documentation less ambiguous.īut thinking further about the wait-for-idle use case, I have found a solution which likely does not even require to change anything in my code. Unfortunately this means that the event is not very useful here. The files in questions are currently being downloaded from the remote device and belong to What did you mean? I suppose the from version. The files in questions are currently being downloaded by the remote device and belong to folder. The files in questions are currently being downloaded on the remote device and belong to folder.

#Syncthing disable dewvice connection notifications download

I also noticed that there’s a Remote Download Progress event. However, I suppose this way of querying completion does not allow to distinguish whether the needed chunks can only be downloaded from the current instance. If waiting for the event isn’t possible, I could also just poll GET /rest/db/completion. For those directory/device combinations which still require bytes, I could then wait for the FolderCompletion event. I could query GET /rest/db/completion for all directories and for all connected devices and check whether those still need bytes. Shutting down once sync completes should be done by checking completion of other devices, not much related to events, as we don’t emit anything useful for the state of other devices.

#Syncthing disable dewvice connection notifications how to

So the “sync is complete” from the perspective of the particular node (which introduced the new versions).Īny other ideas how to improve the two features? That would actually be the required criteria because it would mean I can finally turn off the computer who “introduced” the new versions and the rest of the cluster can still become completely up-to-date on its own. Or maybe is there a way to find out whether each file/chunk/unit has at least been uploaded once? The events ItemStarted and ItemFinished are not useful here because they also only cover downloading if I understand correctly. Since the state sync only means downloading, is there some way to determine whether a directory is uploading? That would be quite useful. I think those features would be useful so I’d like to implement them properly. uploading an album produces a notification for each uploaded track.Īny false statements or misunderstandings on my side so far? How to improve those features? This is very annoying when those notifications are enabled and likely the reason everybody turned them off in the settings. can even happen quite often during upload.

#Syncthing disable dewvice connection notifications update

However, I believe this is only the case because some index update is pulled back which causes the directory to be in status sync only for a short moment.

To implement the notifications, I simply check for the status transition sync ⇨ idle and emit the notification in that case. The idle detection simply checks whether the directory status is idle. Syncthingctl wait-for-idle -timeout 1800000 -at-least 5000 & systemctl poweroff to shutdown after all local changes have been uploaded: Detect when Syncthing really does nothing, eg.Showing notifications when a directory has been synchronized, eg.Who has already tested it has likely noticed, that the following features do not work very well so far: As you likely know I’m developing Syncthing Tray.