Skip to main content

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [List Home]
RE: [platform-team-dev] Lingering synchronize jobs in the progressview.

One request which is very close to what we see is this:
 
https://bugs.eclipse.org/bugs/show_bug.cgi?id=98897
 
Also:
 
https://bugs.eclipse.org/bugs/show_bug.cgi?id=66550
https://bugs.eclipse.org/bugs/show_bug.cgi?id=62995
https://bugs.eclipse.org/bugs/show_bug.cgi?id=68274
https://bugs.eclipse.org/bugs/show_bug.cgi?id=67574
 
Seems to be related to improper handling of IProgressConstants#KEEPONE
property. Some of them are fixed in 3.0 but the problem is still in 3.1.
Anyway, I was just hoping someone would remember the specifics.

Thanks,
Vladimir.


________________________________

From: platform-team-dev-bounces@xxxxxxxxxxx
[mailto:platform-team-dev-bounces@xxxxxxxxxxx] On Behalf Of Michael Valenta
Sent: Tuesday, January 16, 2007 1:45 PM
To: Generic team support framework
Subject: Re: [platform-team-dev] Lingering synchronize jobs in the
progressview.



Vladimir, 

Over the last few releases we have seen issues like this in the Progress
view and many of them have been fixed. However, I cannot find a particular
bug that matches your symptoms. You can browse them yourself if you like
using Platform/UI as the Product/Component and put [Progress] in the Summary
field. 

Michael 




"Vladimir Grishchenko" <vladgri@xxxxxxxxxxx> 
Sent by: platform-team-dev-bounces@xxxxxxxxxxx 

15/01/2007 04:54 PM 
Please respond to
Generic team support framework <platform-team-dev@xxxxxxxxxxx>


To
	<platform-team-dev@xxxxxxxxxxx> 
cc
	
Subject
	[platform-team-dev] Lingering synchronize jobs in the progress view.

	




Hello,

We have our own team provider and noticed that synchronize jobs tend to stay
in the progress view even though they are really finished. A quick bug
search revealed quite a few similar defects reported against CVS and other
components, so this seem to be a generic problem. While I can reliably
reproduce it in 3.0.2 and 3.1.2, 3.2 doesn't have this problem, so the issue
appears to be resolved in the latest release. This may not be the best list
to ask but because the defect was looked at in CVS context may be someone
can kindly point me to the actual bug report whose resolution solved the
issue or provide some insights about it? Because there are so many similar
defects it is hard to find what was actually done to resolve it and when.

Thanks much,
Vladimir.

_______________________________________________
platform-team-dev mailing list
platform-team-dev@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/platform-team-dev





Back to the top