Problem: If I upload content with the name 'abc.png' on the cloud to a folder sync'd to on-prem, then add the same file to the on-prem folder, they become linked as far as the on-prem file is concerned, but the cloud file still says 'sync pending'. This is inconsistent.
1. Upload content with the name 'abc.png' on the cloud to a folder sync'd to on-prem.
2. Upload the same file to the corresponding on-prem folder.
3. The sync will then pend for the on-prem folder and rather than try to create a new file will marry it to the same file in the cloud folder (is that correct behaviour? I'll assume it is), the sync information now shows the link to the same node-ref as the file we uploaded in step one. So this has created a link to the existing cloud copy of the same file and not created a 'abc-1.png' copy.
3a. (Side Note) When I tested with two different files with the same name this threw an error in the logs, but does not present an information this is happening to the user?! (Additional bug?) Just that it is still pending.
4. If I then inspect the sync information for the file created in step 1 it still shows the sync status as 'sync pending'. This is incorrect, as the on-prem version has mapped on the node-ref now??