If rename folder fails, the client is out of sync

This forum is now locked, since Gold Support is no longer offered.

Moderator: SourceGear

Locked
Tim Rayment
Posts: 4
Joined: Thu Dec 06, 2007 10:53 am

If rename folder fails, the client is out of sync

Post by Tim Rayment » Mon Jun 16, 2008 1:59 am

Running 4.1.2.18185 for client and server but have seen this on previous versions.

Scenario - User A tries to rename a folder in which User B has a file checked out.

The operation fails with a "Check In/Commit transaction failed" message. So far so good.

However the folder is renamed on the User A's local machine and the vault client on User A's machine shows the new name. User B's machine still shows the folder with the original name. Restarting Vault client on User A's machine does not fix this.

We've reproduced this several times on a number of machines.

Thanks,

Tim

lbauer
Posts: 9736
Joined: Tue Dec 16, 2003 1:25 pm
Location: SourceGear

Post by lbauer » Mon Jun 16, 2008 11:21 am

The transaction is most likely still in the pending change set.

Find the transaction in the pending change set, right-click and choose Undo. This should undo the rename.

I'll log a bug to look into this behavior, since a Get Latest get the file but renames it, even though it's not renamed in the repository.
Linda Bauer
SourceGear
Technical Support Manager

Tim Rayment
Posts: 4
Joined: Thu Dec 06, 2007 10:53 am

Post by Tim Rayment » Tue Jun 17, 2008 1:53 am

Thanks Linda, I hadn't noticed it was still in the pending change set.

Might it be worth rewording that message box to make it clearer that the change can be undone?

Kind regards,

Tim

lbauer
Posts: 9736
Joined: Tue Dec 16, 2003 1:25 pm
Location: SourceGear

Post by lbauer » Wed Jun 18, 2008 8:24 am

Glad this is resolved. Yes, the message would be helpful, as users may not realize they can undo the change.
Linda Bauer
SourceGear
Technical Support Manager

Locked