Bugzilla – Full Text Bug Listing
| Summary: | [ui] multiple categories listed for same feature??? | ||||||
|---|---|---|---|---|---|---|---|
| Product: | [Eclipse Project] Equinox | Reporter: | Chris Aniszczyk <caniszczyk> | ||||
| Component: | p2 | Assignee: | P2 Inbox <equinox.p2-inbox> | ||||
| Status: | RESOLVED DUPLICATE | QA Contact: | |||||
| Severity: | major | ||||||
| Priority: | P3 | CC: | cpuidle, john.arthorne, Kevin_McGuire, steffen.pingel, susan | ||||
| Version: | 3.4 | ||||||
| Target Milestone: | 3.4 RC3 | ||||||
| Hardware: | PC | ||||||
| OS: | Windows XP | ||||||
| Whiteboard: | |||||||
| Attachments: |
|
||||||
|
Description
Chris Aniszczyk
Created attachment 100774 [details]
multiple personalities :)
Chris, what build are you running? And does it always occur? Also, had you done anything in particular when this happened? (like add or remove a bunch of repos, etc.) I suspect this is some variant of bug #229069. This was with Build id: I20080516-1333 This only occurred when I was adding the site initially. I haven't been able to successfully reproduce it. *** Bug 233362 has been marked as a duplicate of this bug. *** one oddity is that all of us who have seen this (myself, John, Kevin, Chris) have seen it on the Eclemma site. Not sure if that's a coincidence or not. (bulk bug update...) marking RC3. Not sure I could justify a fix during RC3 but the scenario will be tested during RC2 test pass to see how severe the problem is. *** Bug 233602 has been marked as a duplicate of this bug. *** Saw the same error (bug 233602) with the build id that was reported by Chris (comment #4): I20080516-1333 . thanks, Steffan. I understand the nature of the bug, and it is very timing-dependent. And the timing is changing radically as we fix bugs for RC1 and RC2, so I'm going to step back and retest on the RC2 candidate. While its not easy to make happen, it does look pretty unrefined. I had this just now, with the RC2 candidate (1am build). Again it was with eclemma. I noticed that the category appeared with the correct chidren, but the "pending" node was still there. Sometime later the "pending" node was replaced with a duplicate of the category that was already there (with the same IUs underneath). I am almost certain this is caused by the same problem in bug #229069, so I'm marking as a duplicate. The root cause is multiple viewer refreshes happening in succession while running the DeferredTreeContentManager (see bug #226343). In practice, this can happen if you receive a repository add event while expanding a node. Multiple async refreshes get queued up in the UI and if they happen to run in succession, you'll see the duplicate results. I wanted to be sure I understood why adding EclEmma would cause this problem. In checking the eclemma feature jar, I see that its feature.xml defines its update site like this: <update label="EclEmma Updates" url="http://update.eclemma.org/" /> That causes the url (with the trailing slash) to get added. If you added the site previously without the slash, this site was also being added. Having found an explanation for Eclemma to trigger this problem, I'm marking this as a duplicate of bug #229069. *** This bug has been marked as a duplicate of bug 229069 *** *** Bug 234550 has been marked as a duplicate of this bug. *** |