local files vanish after branching/sharing

nmcalpin · Post by **nmcalpin** » Thu Mar 30, 2006 12:01 pm

Steps to reproduce:

create a folder in vault ($/test1/folder1)

create a local folder (c:\test1\folder1)

set the working folder for $/test1/folder1 to c:\test1\folder1

create a few files (1.txt, 2.txt, 3.txt will work fine)

add 1.txt, 2.txt, and 3.txt to $/test1/folder1

GLV $/test1/folder1

create a folder in vault ($/test1/folder2)

share $/test1/folder1 into $/test1/folder2. (This creates $/test1/folder2/folder1)

branch $/test1/folder1

rename $/test1/folder1 to $/test1/folder1OLD

share $/test1/folder2/folder1 to $/test1 (this will create $/test1/folder1)

set working folder for $/test1/folder1 to c:\test1\folder1

look in c:\test1\folder1 and verify files are ok/untouched as expected.

GLV $/test1/folder1

look in c:\test1\folder1 and observe that all files are missing/vanished

GLV $/test1/folder1 again

look in c:\test1\folder1 and see that files are back

this has caused annoyances to our developers many times over the months, any chance of a fix?

lbauer · Post by **lbauer** » Thu Mar 30, 2006 3:13 pm

I wasn't able to reproduce this.

What version of Vault Client and Server are you using?

Where are users storing their state/baseline files (_sgvault folders)? The setting is Tools->Options->Local Files->Cache/Backup Locations.

Mine were in my working directories.

nmcalpin · Post by **nmcalpin** » Thu Mar 30, 2006 3:23 pm

version 3.1.7 client and server.

my client is set to:

store client cache folder:
"in custom folder"
C:\Documents and Settings\Nick\Application Data\SourceGear

store working folder state/baseline files:
"in client cache folder"

lbauer · Post by **lbauer** » Thu Mar 30, 2006 4:32 pm

We had a report from another user of a similar issue, and this was the problem:

If your option to "perform repository deletions locally" is not set to "Do not remove working copy", and you've deleted a repository folder and then added a new folder of the same name, the next time you do a Get it will remove files in that folder that were not retrieved as part of the Get.

In your case, renaming the folder has the same effect as deleting the folder in the case described above. A simple work-around would be to set the "Peform Repository Deletions" to "Do not remove working copy".

We've logged a bug about this behavior and are working to fix it.

dan · Post by **dan** » Wed Jun 07, 2006 8:21 am

FYI, this bug has been addressed in Vault 3.1.9