I'm using Vault as a single user on a single development machine, so I don't use checkin/checkout, I just let the Vault client detect what files I have changed, and add new files/folders when I need to. I've noticed an odd bug and today I think I was able to narrow it down.
When I opened the client today, a file that I had not touched in a while came up as needing a merge. It appeared that Vault was comparing the file to a version 2 updates ago, not the most recent one viewable in the history. I just did "resolve merge status" since I knew the file on my hard drive was the correct one. I can't figure out why it picked today to mess up on a file I haven't edited in months or why it pulled the wrong version up. Unfortunately I have no idea how to replicate this bug.
Vault comparing wrong version of files.
Moderator: SourceGear
I'm almost 100% sure that the _sgvault directory was never deleted. Plus there were a few other files in that directory and none of them came up as needing a merge.lbauer wrote:You can get a "needs merge" status on a modified file in the working directory if the baseline is incorrect. This can happen if the _sgvault hidden state folder was deleted at some point and then recreated.