Community
Participate
Working Groups
Build ID: M20060921-0945 Steps To Reproduce: 1. Synchronise a from-Bugzilla task. 2. Add a comment to that bug 3. Submit to repository Result: mid-air collision detected with previous comment on the same bug, even if that comment is days old. More information: Since upgrading to 0.92, I am unable to add comments to bugs in Bugzilla. Unfortunately, I only have access to one repository at the moment -- after this bug is in Eclipse's bugzilla, I will attempt to reproduce the problem by commenting on this bug.
Commenting on bugs in this Bugzilla appears to work for me. There is one obvious difference between Eclipse's Bugzilla and the Bugzilla against which attempts to comment fail -- the latter requires HTTP authentication to access. If you don't have access to such a Bugzilla for testing, please advise on how I can provide additional information.
Have you tried doing a Synchronize on the bug that's giving you mid-air collisions? http://wiki.eclipse.org/index.php/Mylar_Tips_and_Tricks
If you're using an older Bugzilla (2.18.?) see the last bullet at http://wiki.eclipse.org/index.php/Mylar_FAQ#Bugzilla_Connector_troubleshooting
(In reply to comment #2) Yes -- step (1) in my "steps to reproduce" was "synchronise" :) When I do that _after_ the mid-air collision, I am informed that there are local changes that will be overwritten. I, of course, accept the overwrite to get back in-line with the repository. Subsequent attempts to re-comment on that bug then fail in the same fashion.
(In reply to comment #3) The bugzilla in question appears to be 2.20.1
Could you attach (or send me privately if necessary) sample html of a bug report from your repository. In addition a sample dump of the xml of the same bug report.
(In reply to comment #6) Please advise on how to get the XML for the bug report.
One way is to enter the following to retrieve bug 1 in xml form: <your-repository-url>/show_bug.cgi?id=1&ctype=xml
(In reply to comment #8) Samples sent via email.
Although the bugzilla install is 2.20.1, it appears as though you have the same problem faced on bug#149513: What you get in the browser: 2006-12-08 13:17:56 EST doesn't match what we get in the xml: 2006-12-08 13:17 EST (which is what we have to work with in our client) So unfortunately we don't have the necessary data to send back to bugzilla thus resulting in the mid-air collision. If you wish to investigate further, see comment#37 bug#149513. A starting point would be to check if your tables are in fact using the wrong type for delta_ts (should be datetime). *** This bug has been marked as a duplicate of bug 149513 ***
This is surprising! I didn't have this problem before I upgraded to Mylar 0.92. I am trying to roll-back to 0.91 to see if the problem is present there as well. I don't believe that our bugzilla has changed, but I don't know that for a fact. I will report back shortly.
Reopening. This is not a dupe of bug #149513. I see this problem with Mylar 0.9.2, but with Mylar 0.9.1 I can comment on bugs without problems.
Okay thanks for confirming this Ian, investigating....
I owe you one Ian. Fixed in head. Please confirm with 0.9.2.1 (which should be available within the hour).
Update: You will be able to get the latest at the regular update site and release number is 0.9.2.2. (Available in 20 minutes)
This is fixed for me with 0.9.2.2. Nice going!
Great! Thanks for being persistent on this one Ian, and for confirming that this issue is resolved.
Created attachment 55349 [details] mylar/context/zip
Verified in 0.9.2.2.
Great work.
