Change 13888
Fix for MoveAdd bug where the target file is sync'ed to the incorrect revision of the file before editing.
This results in a pending resolve and a failed submit.
The sync -f is performed on the source server's file path and revision since "file.localIntegSyncSource()" is used. This is incorrect as far as I can see, and should be replaced with "source" since this holds the correct target file and head revision.
#review-13889
@robert_cowham
In a simple test scenario, where both source and target are initally empty, transfer of a move operation will result in identical revision numbers for both target and source, thus masking it's effect. The bug will only occur if the target is of a different head revision number and or path to the source.
This results in a pending resolve and a failed submit.
The sync -f is performed on the source server's file path and revision since "file.localIntegSyncSource()" is used. This is incorrect as far as I can see, and should be replaced with "source" since this holds the correct target file and head revision.
#review-13889
@robert_cowham
In a simple test scenario, where both source and target are initally empty, transfer of a move operation will result in identical revision numbers for both target and source, thus masking it's effect. The bug will only occur if the target is of a different head revision number and or path to the source.