We use version 3.0.7 (2863). I checked out three files, made changes, and checked in. What happened was that vault determined that no changes were made, did not check in, and reloaded my client (visual studio.net) with the previous unchanged code. If it weren't for the _sgbak subdirectory and my noticing that suddenly my changes were gone I would have lost around 6 hours of code changes. Is there something we can do to keep this from happening in the future?
Also, for some files I try to check out and vault tells me that I already have it checked out, does the checkout, tells me that it couldn't check out but the vault client then shows that I checked it out. Has anybody seen this behavior before?
Check in not checking in
Moderator: SourceGear
We've had a few similar reports when users were using folder security and had a large number of checkouts.
I'd suggest upgrading to Vault 3.1.1. We made some changes to checkouts/checkins that could help with the behavior you're seeing.
http://support.sourcegear.com/viewtopic.php?t=4397
I'd suggest upgrading to Vault 3.1.1. We made some changes to checkouts/checkins that could help with the behavior you're seeing.
http://support.sourcegear.com/viewtopic.php?t=4397
Linda Bauer
SourceGear
Technical Support Manager
SourceGear
Technical Support Manager
-
- Posts: 14
- Joined: Wed Jun 23, 2004 9:36 am
- Contact:
don't like this answer
Not sure if I like this answer. Can you:
a) confirm that what Scott is saying is a bug
b) confirm that this is definitely fixed in 3.1.1
I have at least 30 of our developers that have approached me since we upgraded from 2.0 to 3.0.7 with this problem. I think we have lost weeks (collectively) of work because of this MAJOR bug. You guys should probably give me a call ASAP.
Oh, and the original poster of this thread, Scott, works with me at Match.com.
Thanks,
a) confirm that what Scott is saying is a bug
b) confirm that this is definitely fixed in 3.1.1
I have at least 30 of our developers that have approached me since we upgraded from 2.0 to 3.0.7 with this problem. I think we have lost weeks (collectively) of work because of this MAJOR bug. You guys should probably give me a call ASAP.
Oh, and the original poster of this thread, Scott, works with me at Match.com.
Thanks,
_________________________
Shane Henderson, MCAD
Technical Architect
Match.com
shane.henderson@match.com
Shane Henderson, MCAD
Technical Architect
Match.com
shane.henderson@match.com
We'd need more information before we could determine what the problem is. We can call you -- send me your phone number via the email link below or email Linda @sourcegear.com.Can you:
a) confirm that what Scott is saying is a bug
b) confirm that this is definitely fixed in 3.1.1
Linda Bauer
SourceGear
Technical Support Manager
SourceGear
Technical Support Manager