Community
Participate
Working Groups
TaskWorkingSetUpdater is occasionally failing upon activating task
Created attachment 72995 [details] stack trace
Mik, I assume you want to look at this one.
Eugene: if you have any steps to reproduce put them on bug 194917. I'll be investigating this soon but haven't been able to reproduce it yet. *** This bug has been marked as a duplicate of bug 194917 ***
(In reply to comment #3) > Eugene: if you have any steps to reproduce put them on bug 194917. I'll be > investigating this soon but haven't been able to reproduce it yet. No idea how to reproduce. It just happens few times. I have maybe 10 regular resource working sets and about 5 Mylyn ones, though I don't select any resources in those. Maybe it is related to that weird logic about updating working sets when task is activated (i.e. add its category/query there). I am still not sure if it is a good idea, because I created working sets for a reason and don't need them to be changed, even if some task been opened from Sync or history view or hyperlinked from other bugs.
So you are still using separate resource and working sets instead of just the Mylyn ones? I stopped doing that, Shawn didn't, and he saw this error, so I wonder if it's related to that. Regarding the auto-activation policy, yup, it is likely that it needs some refinement. But the current policy is to activate the working set for that task if the task is activated, so the thing that you describe sounds like it could be a sideffect of this bug or a different bug.
(In reply to comment #5) > So you are still using separate resource and working sets instead of just the > Mylyn ones? Of course. Resources and tasks are completely orthogonal. Besides, Package Explorer don't want to do anything with Mylun's working sets.
(In reply to comment #6) > Besides, Package Explorer don't want to do anything with Mylun's working sets. See top of New & Noteworthy for how to configure the Package Explorer to show Mylyn's combined task+resource working sets.
(In reply to comment #7) > See top of New & Noteworthy for how to configure the Package Explorer to show > Mylyn's combined task+resource working sets. From what I see, the top of New & Noteworthy has screenshot of the welcome screen. Anyways, like I said, I don't see how I can overlap my 8 project working sets and 5 task working sets and like to keep them separate. I also believe that it is responsibility of the Platform to handle non-resource working sets and generally any alien working sets correctly, which someone should bring up on the cross project list. Though I probably already mention that few times.
To clarify. When I was referring to the Package Explorer I was talking about "Top level elements / working sets" mode.
