9 messages in com.perforce.perforce-user[p4] Perforce dropping important stuff| From | Sent On | Attachments |
|---|---|---|
| Kimberly McClintock | 10 Jul 2001 07:17 | |
| Chris Patti | 10 Jul 2001 09:08 | |
| Jeff A. Bowles | 10 Jul 2001 10:33 | |
| Stephen Vance | 10 Jul 2001 11:05 | |
| Kimberly McClintock | 10 Jul 2001 12:18 | |
| Russell C. Jackson | 10 Jul 2001 13:03 | |
| Steve Cogorno | 10 Jul 2001 13:07 | |
| ste...@vance.com | 10 Jul 2001 13:08 | |
| Long Doan | 10 Jul 2001 13:20 |
| Subject: | [p4] Perforce dropping important stuff |
|---|---|
| From: | Long Doan (ldo...@multicitycorp.com) |
| Date: | 07/10/2001 01:20:25 PM |
| List: | com.perforce.perforce-user |
[This only applies if your engineers are using VisualCafe]
If so, when you edit a file using VisualCafe, and it determines that your file needs to be refresh, it syncs AND DOES NOT refresh its edit buffer. So, when the user performs the edit and save, all changes up to the latest version are lost.
Hope that helsp, Long.
-----Original Message----- From: Kimberly McClintock [mailto:kmcclintock at aegiscorp.com] Sent: Tuesday, July 10, 2001 3:18 PM To: 'Jeff A. Bowles'; 'perforce-user at perforce.com' Subject: RE: [p4] Perforce dropping important stuff
Jeff -
Some clarification since this morning: What we are actually seeing is:
Joe checks out a file, edits it & checks it back in via a numbered changelist. This becomes #4. Eric syncs, checks the same file out, edits it & checks it back in. This becomes #5. In half a dozen cases we have noticed, after the fact, that Eric's file #5 overwrote the changes in file #4; no other files in the changelist were affected. This is evident when you diff the revisions.
We have only seen this behavior within changelists & engineers are checking to see if it's single files in a changelist or the whole thing.
Any takers on that one?
Tech support is involved. Thank you for addressing the bug list question, I have gotten a hold of the fixed ones.
Kimberly
-----Original Message----- From: Jeff A. Bowles [mailto:jab at piccoloeng.com] Sent: Tuesday, July 10, 2001 11:34 AM To: Kimberly McClintock; 'perforce-user at perforce.com' Subject: Re: [p4] Perforce dropping important stuff
At 08:18 AM 7/10/2001 -0600, Kimberly McClintock wrote:
I have a situation: Our engineers have seen the following: Perforce dropping files from a changelist; Perforce dropping changes from a file on merge.
Wonder if anyone's seen the likes of this before? If there is a "known bug" list out there somewhere?
Get thee to Tech Support. These are questions that you want quick answers to, from folks who might've heard of them [from another customer] already.
Dropping files from a changelist doesn't sound familiar. There is a situation where you might have it drop modifications from a merge, which is understandable with a bit more information and MIGHT be what you're talking about:
* You open a file in a way that "schedules a resolve". (In other words, you open it for edit and it's not the most current revision that you're editing and then you try to 'p4 submit', or you open for integrate. The term "schedules a resolve" translates to "writes some temporary things to the database saying that when you run 'p4 resolve' that it'll be pulling content from somewhere and identifies the YOURS/THEIRS/BASE revisions that'll drive the resolve.")
* During the resolve, you select the "lazy copy" option - which is "accept theirs".
* You erroneously assume that Perforce will take the local copy of the file when you submit, and check it in, so you make it writeable ("chmod" or setting the write attribute on the file) and add a few quiet hacks to the file.
* You submit it, and then when you look, you see that your extra hacks from the previous step - made outside of 'p4 resolve' - aren't there. (By the nature of "accept theirs", they're not supposed to be. But it's tough to explain that to the person who hacked the file in the previous step.)
I can't say that you're running into this, because you didn't give a lot of background in your question.
Anyhow, follow this up to support at perforce.com....
-Jeff Bowles Perforce Consulting Partner
ps. I don't know of a "known bug" list for the Perforce product. There is the "fixed bugs" list (along with new features) in the release notes.