Re: Alert! Issue has been modified, please review before submitting your changes.
Ларионов Андрей <[email protected]>
| Newsgroups | gmane.comp.java.scarab.user |
|---|---|
| Message-ID | <[email protected]> |
I think we should store version (invrementing value) instead of timestamp. Propose to inclusion in 0.22 ________________________________ From: Jorge Uriarte Aretxaga [mailto:[email protected]] Sent: Thursday, February 07, 2008 5:06 PM To: [email protected] Subject: Re: Alert! Issue has been modified, please review before submitting your changes. I don think so. Funny lateral effect, btw... I wonder if we could shield Scarab against that kind of behaviour... _ Jorge On 2/7/08, Mikael Brodd <[email protected]> wrote: Ah, yes you are right! The server clock was out of sync this morning and at 9 am Swedish time stated 2 pm. It was then corrected. So I have tried to change a defect at 11 am, which has a timestamp of 2 pm. So, if we just wait and change the defects after latest-change time, it should be fine, right? ________________________________ Frеn: Jorge Uriarte Aretxaga [mailto:[email protected]] Skickat: den 7 februari 2008 11:50 Till: [email protected] Дmne: Re: Alert! Issue has been modified, please review before submitting your changes. What can you tell me about the date & time of the server? Collision detection is based on timestamps... did you change anything on that area today? Can you take a look at the last modification time of the affected issues? _ Jorge On 2/7/08, Mikael Brodd <[email protected]> wrote: Yes, you assume right. We are not editing the same issue simultaneously and I cannot submit the changes. It does not happen on all defects. I can create defects and they work fine all the way through. I have narrowed the problem down to the defects I have changed earlier today actually.