db.Counts understandig receiveOnlyChangedDeletes

I made some tests in doing manually some changes to a receiveonly and a receiveencrypted folder (done individually and then reverted).

After reverting the changes via UI button, I get following result via API:

Receiveonly folder

curl --silent -H "X-API-Key: ${AKEY}" "http://127.0.0.1:22007/rest/config/folders/${FOLDER}"|grep type|head -1
  "type": "receiveonly",

with

curl --silent -H "X-API-Key: ${AKEY}" "http://127.0.0.1:22007/rest/db/status?folder=${FOLDER}"|grep "receiveOnlyChanged.*:"
  "receiveOnlyChangedBytes": 0,
  "receiveOnlyChangedDeletes": 0,
  "receiveOnlyChangedDirectories": 0,
  "receiveOnlyChangedFiles": 0,
  "receiveOnlyChangedSymlinks": 0,

and for the receiveencrypted folder (on a second device)

curl --silent -H "X-API-Key: ${AKEY}" "http://127.0.0.1:22007/rest/config/folders/${FOLDER}"|grep type|head -1
  "type": "receiveencrypted",

with

curl --silent -H "X-API-Key: ${AKEY}" "http://127.0.0.1:22007/rest/db/status?folder=${FOLDER}"|grep "receiveOnlyChanged.*:"
  "receiveOnlyChangedBytes": 0,
  "receiveOnlyChangedDeletes": 1,
  "receiveOnlyChangedDirectories": 0,
  "receiveOnlyChangedFiles": 0,
  "receiveOnlyChangedSymlinks": 0,

This queries were done with all nodes in sync. I wonder why receiveOnlyChangedDeletes is different? Both manipulation tests before were done by adding files manually and then revert everything again via UI.

The motivation is to query for changes and then “resetting” it. In the latter case changes would be detected without actually having such “manipulations”.

Any hints? Thanks!

Might be a bug. From the top of my head I expect it to mean things which have been deleted from a recv-only folder.

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