Checkin sometimes undoes checkout
Moderator: SourceGear
Checkin sometimes undoes checkout
I thought I was crazy...but then I told my problem to some coworkers and they said the same was happening to them. It's a straightforward problem. Sometimes when I check in a file that I've edited and saved, Vault 3.0.1 prompts me for a comment and then it happily undoes the checkout. My edited file goes to sgbak and there's a nice entry in the log of the undo checkout. I do not know if the "edited" flag was showing in the GUI before I selected check in. All I know is it's causing problems...
Am I crazy?
Am I crazy?
Only your close friends can answer that one.Am I crazy?
I tried to reproduce this, but it didn't happen. Can you reproduce it? If so, let us know the specific set of steps leading up to the strange behavior.
If you can't reproduce, next time it happens see if you can recall what you were doing, what the status was of the file that you were trying to check in, and any other details.
Linda Bauer
SourceGear
Technical Support Manager
SourceGear
Technical Support Manager
I'll pay attention next time...unfortunately it doesn't happen often and when it does, I usually notice much later when the version is wrong.
I can, however, guarantee that it is happening. The one piece of information I don't know is if the file indicated that it was edited in Vault (it had changed, and the new version was happily sitting in the sgbak folder). I don't suppose it's as straightforward as you're missing a refresh right before a check in?
I can, however, guarantee that it is happening. The one piece of information I don't know is if the file indicated that it was edited in Vault (it had changed, and the new version was happily sitting in the sgbak folder). I don't suppose it's as straightforward as you're missing a refresh right before a check in?
I would suggest turning on client logging (see http://support.sourcegear.com/viewtopic.php?t=2146) and the next time it happens, save off the log, and try to identify which entries correspond. The log will grow quite large, so you may want to delete it once a day. We may need to send out a temp build with more logging in it if there isn't enough info (and you see the problem often enough to reproduce it occasionally)
Some questions:
1. Do both of you have the "require comments" feature turned on?
2. Is this happening through the GUI client, the IDE client or both?
3. Do either of you use CRCs to determine whether a file has been edited?
Some questions:
1. Do both of you have the "require comments" feature turned on?
2. Is this happening through the GUI client, the IDE client or both?
3. Do either of you use CRCs to determine whether a file has been edited?
Re: Checkin sometimes undoes checkout
We have also experienced this problem with Vault 2.06. This happened on files within a shared project. Is it the same for you?awdavis wrote:Sometimes when I check in a file that I've edited and saved, Vault 3.0.1 prompts me for a comment and then it happily undoes the checkout. My edited file goes to sgbak and there's a nice entry in the log of the undo checkout. I do not know if the "edited" flag was showing in the GUI before I selected check in. All I know is it's causing problems...?
File, from within VS2003, right click, check in. Sometimes, I checked in multiples files. All files outside of the shared project are checked in OK. Only the file in the shared folder was affected (the check-in became undo check out. Fortunately, the latest version was saved in _sgbak). The trouble was that this didn't happen systematically.bfinney wrote:Tri: Do you recall how you invoked the checkin - was it on a file, or a folder, or in the change set?
I have also had this problem. I have tried to reproduce, but cannot. I am not positive, but i think it occured with files that I was editing- tried to save- they were read only- so while RO warning was up I checked out- then completed save.
I know the files were changed on disk- projects were rebuilt, change was realized. I know on checkin, the changes were undone.
I've had it happen maybe 3 times in 3 months. Very infrequent, but shakes one's confidence.
I know the files were changed on disk- projects were rebuilt, change was realized. I know on checkin, the changes were undone.
I've had it happen maybe 3 times in 3 months. Very infrequent, but shakes one's confidence.
Something to verify with everyone: This only happens when checking in files from within Visual Studio, correct?
Another question: Does it seem to happen on file combinations (such as .cs/.resx or .cs/.aspx) were Visual Studio checks out/in two files at the same time, even though it only looks like one file?
Another question: Does it seem to happen on file combinations (such as .cs/.resx or .cs/.aspx) were Visual Studio checks out/in two files at the same time, even though it only looks like one file?
We were using Vault V3.0.0.1 with CRC check set. It happened on VStudio 6.0 .dsp files, when asking the developer he can't recall if he checked them in via Vault Client or VStudio 6.0.dan wrote:Something to verify with everyone: This only happens when checking in files from within Visual Studio, correct?
Another question: Does it seem to happen on file combinations (such as .cs/.resx or .cs/.aspx) were Visual Studio checks out/in two files at the same time, even though it only looks like one file?
Not much, i hope it helps.... We appreciate the support you offer....