Community
Participate
Working Groups
Automatic synchronization crashes the workbench. Here's how to reproduce the bug: Use latest 1.0 version (but I had the same problem with the 0.9 one too...), Bugzilla connector. 1. Create a query that returns no results (maybe because there are no bugs yet in that repository), or maybe takes too long to complete (the bug seems to happen when there are more than one queries running, while one query somehow is blocked(?) by the other one). Example: http://www.karakas-online.de/various/mylar-new-query.jpg 2. Set automatic synchronization, say every 1 minute, or every 5 minutes. The query starts the synchronization, but takes too long somehow - it seems that it never returns, the progress bar stays there empty for ever: http://www.karakas-online.de/various/mylar-synchronizing-new-empty-query.jpg 3. While the first query is still running, start a new one. In the upcoming dialog, choose "update products from the repository": http://www.karakas-online.de/various/mylar-new-query-while-synchronizing-empty-query.jpg 4. The dialog never lets you continue. It tries to update the products from the repository for ever. You cannot cancel, because all buttons are disabled: http://www.karakas-online.de/various/mylar-update-products-for-ever.jpg 5. You cannot do anything, while the second query runs for ever and blocks the dialog - and you cannot do anything more. If you try, you get an error saying that the "Wizard cannot be closed due to an active operation. You must cancel the operation before you can close the wizard" - but as said, you cannot cancel because all buttons are grayed... http://www.karakas-online.de/various/mylar-update-products-cannot-cancel.jpg 6. Some time later, the workbench crashes. Chris Karakas http://www.karakas-online.de
This could be a concurrency problem that is already resolved (bug 167402), in which case you should not be able to reproduce it in today's upcoming 1.0.1 release. If that is not the problem, we will have to investigate why the original query is getting stuck. Does the deadlock still happen if the query does not get stuck? Marking down severity since there is a clear work-around in not creating queries while another is running.
I installed 1.0.1 today. I will look how it behaves in the time "between the years" and report "next year". In the meantime, happy holidays to all of you! :-) Chris Karakas http://www.karakas-online.de
Well, as far as this bug is concerned, Mylar seems to work OK now. I think we can close this bug.
