Files sometimes go renegade during move

gsmalter · Post by **gsmalter** » Mon Mar 10, 2008 10:02 am

First I'd like to say that moving files in VS2008/4.1/enhanced client is way, way better than it was in 3.x/Classic Client, and it usually works great.

Sometimes, though, every file I drag in Visual Studio immediately becomes renegade. Sometimes not, though. I'm not sure what causes this.

lbauer · Post by **lbauer** » Mon Mar 10, 2008 10:54 am

Do you notice any pattern? Can you reproduce this? If so, we'd like steps to reproduce.

ian_sg · Post by **ian_sg** » Mon Mar 10, 2008 10:59 am

I'd also like to know, when the file goes renegade, what differences does it show, compared to the baseline? Is it always a particular file type?

gsmalter · Post by **gsmalter** » Mon Mar 10, 2008 11:22 am

I don't know. If I could reproduce it, I would have given the steps.

I can say that the one diff I did do showed no differences (so I don't know why it was classified as renegade).

Also, prior to the problem happening, I was successfully dragging folders without any problem. After it happened once, it now happens almost every time.

I'm able to resolve the problem by just manually checking all of the files out.

ian_sg · Post by **ian_sg** » Wed Mar 12, 2008 10:25 am

Without any other clues, I can only suggest that you turn on the diagnostic logging, and send us a log when it happens again.

gsmalter · Post by **gsmalter** » Wed Mar 12, 2008 10:28 am

The last few times I've tried, I haven't experienced the problem at all. I will get back to you if I see it again, and see a pattern.

Thanks.

gsmalter · Post by **gsmalter** » Thu Dec 03, 2009 1:51 pm

The pattern is that if you move things and do a check-in right away, you are fine. If you wait long enough (could be longer than a day, I'm not sure), then they will eventually go renegade.

lbauer · Post by **lbauer** » Fri Dec 04, 2009 12:11 pm

That's strange. Is this still consistently happening?
Could something be changing the timestamp of the file after you've moved it?
When you say it changes the next day, is this with the client sitting idle, or have you been doing a lot of work with Vault during this time?

Renegade means Vault thinks the file has been modified, and it's not checked out.

Ian suggested turning on client-side logging, so that might be the next step in troubleshooting.

http://support.sourcegear.com/viewtopic.php?p=5375

We'd like to see the log from the time period of the move and then the change to renegade. This could be a pretty huge log

SourceGear Support

Files sometimes go renegade during move

Files sometimes go renegade during move

Re: Files sometimes go renegade during move

Re: Files sometimes go renegade during move