Under certain circumstances where .tmp files are used, file is not synced

[FourEyedPanda]

Some WebDav programs edit a file by first saving a .tmp version and then deleting the actual file and then moving it over to make sure no data is loss.

In ajxp_changes this is shown by:

seq, repository_identifier, node_id, type, source, target '349', 'xxx', '231', 'create', 'NULL', '/xxx/example.txt.tmp' '350', 'xxx', '230', 'path', '/xxx/example.txt', '/recycle_bin/example.txt' '351', 'xxx', '231', 'path', '/xxx/example.txt.tmp', '/xxx/example.txt'

So it:

Creates temp file Moves actual file to recycle bin Moves temp file to actual file name.

This should still be synced. If anything is type path where target is that file it should be synced again. The only thing that seems to overwrite is type of content.

PydioSync v1.2.9 - Windows

[7omate]

What behavior did you witness? Did you look at the exclusion list in the task settings?

[FourEyedPanda]

.,/.,/recycle_bin,.pydio_dl,.DS_Store,.~lock.,~,.xlk,.tmp

Would this exclude syncing a file that was a .tmp and moved to a non .tmp? I still see the same behavior that was *.tactipart and that is not excluded.

Behavior shows in ajxp_changes. The files are too small for me to see what is actually happening. A file of example.txt.tmp was created followed by deletion of original example.txt and then finally renaming example.txt.tmp to example.txt, a non tmp file.