Sync stuck at 95% 0B


i’ve got two client with a shared folder that are stuck on 95% with 0B to sync.

  • I use a .stignore
  • I have clean synced the folder in the past, and did not change anything in .stignore
  • It’s a send and receive folder
  • Local and global states show show the same file count on both sides
  • Sending side shows 0 out of sync items
  • Receiving side looks like it’s cleanly synced
  • File systems are the same on botch sides (ntfs)

Im quite at a loss what could be the issue here, if there is an issue at all. Is there any way (log) to check if there is out-of sync files or could this be an ui bug of some sort ?

Screenshots from both sides would help. Are ignores the same on both sides?

The folder contains mercurial repositories, and i have the .st folders and files ignored from sync. stignore is only present on the sending side.

// mercurial

// IIS Config

Sending side: folder

Sending side: out of sync items

Receiving side: folder

ping @imsodin

That means that you have deleted something on the sending side, that was not yet deleted on the receiving side - do you use the ignore deletes option?

The out of sync items display for remote devices does not handle deleted files - thanks for uncovering this. See issue and PR.

Nope, wasn’t even aware of that option, but rechecked both sides nonetheless.

Hmm, no idea what the problem is then. Can you run curl -X GET -H "X-API-Key: yourapikey" 'http://localhost:8384/rest/db/completion?device=deviceid&folder=folderid' | json_pp on the sending side with the device id of the receiving side? That should list the file that it thinks is missing.

The output unfortunatly does not list which file is needed, but it is indeed a delete:

“globalBytes” : 142701740, “completion” : 95, “needDeletes” : 1, “needItems” : 0, “needBytes” : 0

If this ever comes up again, here is the powershell equivalent of the curl command:

(Invoke-WebRequest -Method Get -Headers @{"X-API-Key"="API-Key"} -Uri "http://localhost:8384/rest/db/completion?device=DEVICE-ID&folder=FOLDER-ID").Content | ConvertFrom-Json

Sorry, I stated the wrong endpoint, it should have been /rest/db/remoteneed (all parameters are the same).

Thanks, it was web.config that is in my .stignore. Resolved the issue by:

  • delete web.config from synced folder
  • remove web.config from .stignore
  • rescan / resync
  • add web.config to .stignore
  • rescan / resync
  • restore web.config

Everything synced up now :slight_smile: Thanks again!

I’ll be sure to utilize the rest api in future for self-debugging.

1 Like

So is there a bug, or is there not a bug @imsodin?

There is at least one bug, that I reported and hopefully fixed (as in the linked issues and PR). That a file that was ignored was reported as out of sync might be one more bug, but given the information available I can’t be sure. And given that mt7479 already resolved its issue, it is not likely that there is going to be more evidence to dig for another bug.

Sorry for jumping the gun on this one. But since ignores where involved is assumed the error is likely going to be on my side.

If this ever occurs again i’ll will report back and we can do proper debugging without prior intervention on my side.

This topic was automatically closed 30 days after the last reply. New replies are no longer allowed.