11:10 a.m.
Max Rydahl Andersen created JBIDE-10979:
-------------------------------------------
Summary: importing project into workspace.... stays around forever
Key: JBIDE-10979
URL: https://issues.jboss.org/browse/JBIDE-10979
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: openshift
Reporter: Max Rydahl Andersen
Assignee: Andre Dietisheim
Priority: Critical
Fix For: 3.3.0.Beta1
the progroess monitor seem to never get closed/finished in case of errors - could we get
those always closed in final block/wizard closing to avoid it always overriding any other
status updates
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
4:14 a.m.
[
https://issues.jboss.org/browse/JBIDE-10979?page=com.atlassian.jira.plugi...
]
Max Rydahl Andersen updated JBIDE-10979:
----------------------------------------
Priority: Blocker (was: Critical)
importing project into workspace.... stays around forever
---------------------------------------------------------
Key: JBIDE-10979
URL: https://issues.jboss.org/browse/JBIDE-10979
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: openshift
Reporter: Max Rydahl Andersen
Assignee: Andre Dietisheim
Priority: Blocker
Fix For: 3.3.0.Beta1
the progroess monitor seem to never get closed/finished in case of errors - could we get
those always closed in final block/wizard closing to avoid it always overriding any other
status updates
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
10:20 a.m.
[
https://issues.jboss.org/browse/JBIDE-10979?page=com.atlassian.jira.plugi...
]
Andre Dietisheim commented on JBIDE-10979:
------------------------------------------
to me it happens always, not only if the import encouters some errors.
importing project into workspace.... stays around forever
---------------------------------------------------------
Key: JBIDE-10979
URL: https://issues.jboss.org/browse/JBIDE-10979
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: openshift
Reporter: Max Rydahl Andersen
Assignee: Xavier Coulon
Priority: Blocker
Fix For: 3.3.0.Beta1
the progroess monitor seem to never get closed/finished in case of errors - could we get
those always closed in final block/wizard closing to avoid it always overriding any other
status updates
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
10:30 a.m.
[
https://issues.jboss.org/browse/JBIDE-10979?page=com.atlassian.jira.plugi...
]
Andre Dietisheim edited comment on JBIDE-10979 at 2/22/12 11:29 AM:
--------------------------------------------------------------------
to me it happens always, not only if the import encouters some errors. I still have no
clue what's wrong here...
was (Author: adietish):
to me it happens always, not only if the import encouters some errors.
importing project into workspace.... stays around forever
---------------------------------------------------------
Key: JBIDE-10979
URL: https://issues.jboss.org/browse/JBIDE-10979
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: openshift
Reporter: Max Rydahl Andersen
Assignee: Xavier Coulon
Priority: Blocker
Fix For: 3.3.0.Beta1
the progroess monitor seem to never get closed/finished in case of errors - could we get
those always closed in final block/wizard closing to avoid it always overriding any other
status updates
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
2:07 p.m.
[
https://issues.jboss.org/browse/JBIDE-10979?page=com.atlassian.jira.plugi...
]
Andre Dietisheim commented on JBIDE-10979:
------------------------------------------
after fiddling for some time if have the slight impression that this is due to the
following:
We build a delegating progress monitor that holds references to the monitor of the job and
the monitor of the wizard dialog. This allows us to have subtasks reported to both (to the
status-bar in the workbench window and the wizard dialog).
When we call monitor#done, the progress monitor of the wizard dialog is already closed and
ends up in a SWTException "widget disposed" when the delegating monitor
delegates to the monitor of the wizard. That's at least how I would explain the
following execption I was able to catch:
{quote}org.eclipse.swt.SWTException: Failed to execute runnable
(org.eclipse.swt.SWTException: Widget is disposed)
at org.eclipse.swt.SWT.error(SWT.java:4282)
at org.eclipse.swt.SWT.error(SWT.java:4197)
at org.eclipse.swt.widgets.Synchronizer.runAsyncMessages(Synchronizer.java:138)
at org.eclipse.swt.widgets.Display.runAsyncMessages(Display.java:3563)
at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:3212)
at org.eclipse.ui.internal.Workbench.runEventLoop(Workbench.java:2696)
at org.eclipse.ui.internal.Workbench.runUI(Workbench.java:2660)
at org.eclipse.ui.internal.Workbench.access$4(Workbench.java:2494)
at org.eclipse.ui.internal.Workbench$7.run(Workbench.java:674)
at org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:332)
at org.eclipse.ui.internal.Workbench.createAndRunWorkbench(Workbench.java:667)
at org.eclipse.ui.PlatformUI.createAndRunWorkbench(PlatformUI.java:149)
at org.eclipse.ui.internal.ide.application.IDEApplication.start(IDEApplication.java:123)
at org.eclipse.equinox.internal.app.EclipseAppHandle.run(EclipseAppHandle.java:196)
at
org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.runApplication(EclipseAppLauncher.java:110)
at
org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.start(EclipseAppLauncher.java:79)
at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:344)
at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:179)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:597)
at org.eclipse.equinox.launcher.Main.invokeFramework(Main.java:622)
at org.eclipse.equinox.launcher.Main.basicRun(Main.java:577)
at org.eclipse.equinox.launcher.Main.run(Main.java:1410)
at org.eclipse.equinox.launcher.Main.main(Main.java:1386)
Caused by: org.eclipse.swt.SWTException: Widget is disposed
at org.eclipse.swt.SWT.error(SWT.java:4282)
at org.eclipse.swt.SWT.error(SWT.java:4197)
at org.eclipse.swt.SWT.error(SWT.java:4168)
at org.eclipse.swt.widgets.Widget.error(Widget.java:466)
at org.eclipse.swt.widgets.Widget.checkWidget(Widget.java:403)
at org.eclipse.swt.widgets.Label.setText(Label.java:571)
at org.eclipse.jface.wizard.ProgressMonitorPart.done(ProgressMonitorPart.java:184)
at
org.eclipse.jface.operation.AccumulatingProgressMonitor$2.run(AccumulatingProgressMonitor.java:163)
at org.eclipse.swt.widgets.RunnableLock.run(RunnableLock.java:35)
at org.eclipse.swt.widgets.Synchronizer.runAsyncMessages(Synchronizer.java:135)
... 23 more
{quote}
importing project into workspace.... stays around forever
---------------------------------------------------------
Key: JBIDE-10979
URL: https://issues.jboss.org/browse/JBIDE-10979
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: openshift
Reporter: Max Rydahl Andersen
Assignee: Xavier Coulon
Priority: Blocker
Fix For: 3.3.0.Beta1
the progroess monitor seem to never get closed/finished in case of errors - could we get
those always closed in final block/wizard closing to avoid it always overriding any other
status updates
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
3:09 p.m.
[
https://issues.jboss.org/browse/JBIDE-10979?page=com.atlassian.jira.plugi...
]
Andre Dietisheim commented on JBIDE-10979:
------------------------------------------
so the solution is to not report to the delegating progress monitor in the wizard utily
(only report to it in the job) since when the wizardutils wants to invoke #done on the
delegating monitor, the job will be terminated and cause the beforementioned exception.
I tested my changes and the status bar in the workbench window is now updated correctly.
@Max: please review my patch
importing project into workspace.... stays around forever
---------------------------------------------------------
Key: JBIDE-10979
URL: https://issues.jboss.org/browse/JBIDE-10979
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: openshift
Reporter: Max Rydahl Andersen
Assignee: Xavier Coulon
Priority: Blocker
Fix For: 3.3.0.Beta1
the progroess monitor seem to never get closed/finished in case of errors - could we get
those always closed in final block/wizard closing to avoid it always overriding any other
status updates
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
3:11 p.m.
[
https://issues.jboss.org/browse/JBIDE-10979?page=com.atlassian.jira.plugi...
]
Andre Dietisheim updated JBIDE-10979:
-------------------------------------
Attachment: dont-report-to-delegatingmonitor-in-wizardutils.patch
importing project into workspace.... stays around forever
---------------------------------------------------------
Key: JBIDE-10979
URL: https://issues.jboss.org/browse/JBIDE-10979
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: openshift
Reporter: Max Rydahl Andersen
Assignee: Xavier Coulon
Priority: Blocker
Fix For: 3.3.0.Beta1
Attachments: dont-report-to-delegatingmonitor-in-wizardutils.patch
the progroess monitor seem to never get closed/finished in case of errors - could we get
those always closed in final block/wizard closing to avoid it always overriding any other
status updates
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
4:57 p.m.
[
https://issues.jboss.org/browse/JBIDE-10979?page=com.atlassian.jira.plugi...
]
Andre Dietisheim updated JBIDE-10979:
-------------------------------------
Attachment: dont-report-to-delegatingmonitor-in-wizardutils-2.patch
@Max: updated my patch. no changes in API, still passing the delegate monitor in so that
wizardutils can add the wizard monitor to the delegate (and updates in the job makes it to
the wizard). But still calling #beingTask and #done on the wizard monitor only (since
these are handled by the job anyway and would cause the beforementioned exception)
importing project into workspace.... stays around forever
---------------------------------------------------------
Key: JBIDE-10979
URL: https://issues.jboss.org/browse/JBIDE-10979
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: openshift
Reporter: Max Rydahl Andersen
Assignee: Max Rydahl Andersen
Priority: Blocker
Fix For: 3.3.0.Beta1
Attachments: dont-report-to-delegatingmonitor-in-wizardutils-2.patch,
dont-report-to-delegatingmonitor-in-wizardutils.patch
the progroess monitor seem to never get closed/finished in case of errors - could we get
those always closed in final block/wizard closing to avoid it always overriding any other
status updates
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
5:01 p.m.
[
https://issues.jboss.org/browse/JBIDE-10979?page=com.atlassian.jira.plugi...
]
Andre Dietisheim edited comment on JBIDE-10979 at 2/22/12 5:59 PM:
-------------------------------------------------------------------
after fiddling for some time if have the slight impression that this is due to the
following:
We build a delegating progress monitor that holds references to the monitor of the job and
the monitor of the wizard dialog. This allows us to have subtasks reported to both (to the
status-bar in the workbench window and the wizard dialog).
When we call monitor#done, the progress monitor of the job is already gone, since the job
has finished and it then tries to update a progress bar that is not present any more (in
the progress view). This ends up in a SWTException "widget disposed":
{quote}org.eclipse.swt.SWTException: Failed to execute runnable
(org.eclipse.swt.SWTException: Widget is disposed)
at org.eclipse.swt.SWT.error(SWT.java:4282)
at org.eclipse.swt.SWT.error(SWT.java:4197)
at org.eclipse.swt.widgets.Synchronizer.runAsyncMessages(Synchronizer.java:138)
at org.eclipse.swt.widgets.Display.runAsyncMessages(Display.java:3563)
at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:3212)
at org.eclipse.ui.internal.Workbench.runEventLoop(Workbench.java:2696)
at org.eclipse.ui.internal.Workbench.runUI(Workbench.java:2660)
at org.eclipse.ui.internal.Workbench.access$4(Workbench.java:2494)
at org.eclipse.ui.internal.Workbench$7.run(Workbench.java:674)
at org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:332)
at org.eclipse.ui.internal.Workbench.createAndRunWorkbench(Workbench.java:667)
at org.eclipse.ui.PlatformUI.createAndRunWorkbench(PlatformUI.java:149)
at org.eclipse.ui.internal.ide.application.IDEApplication.start(IDEApplication.java:123)
at org.eclipse.equinox.internal.app.EclipseAppHandle.run(EclipseAppHandle.java:196)
at
org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.runApplication(EclipseAppLauncher.java:110)
at
org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.start(EclipseAppLauncher.java:79)
at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:344)
at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:179)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:597)
at org.eclipse.equinox.launcher.Main.invokeFramework(Main.java:622)
at org.eclipse.equinox.launcher.Main.basicRun(Main.java:577)
at org.eclipse.equinox.launcher.Main.run(Main.java:1410)
at org.eclipse.equinox.launcher.Main.main(Main.java:1386)
Caused by: org.eclipse.swt.SWTException: Widget is disposed
at org.eclipse.swt.SWT.error(SWT.java:4282)
at org.eclipse.swt.SWT.error(SWT.java:4197)
at org.eclipse.swt.SWT.error(SWT.java:4168)
at org.eclipse.swt.widgets.Widget.error(Widget.java:466)
at org.eclipse.swt.widgets.Widget.checkWidget(Widget.java:403)
at org.eclipse.swt.widgets.Label.setText(Label.java:571)
at org.eclipse.jface.wizard.ProgressMonitorPart.done(ProgressMonitorPart.java:184)
at
org.eclipse.jface.operation.AccumulatingProgressMonitor$2.run(AccumulatingProgressMonitor.java:163)
at org.eclipse.swt.widgets.RunnableLock.run(RunnableLock.java:35)
at org.eclipse.swt.widgets.Synchronizer.runAsyncMessages(Synchronizer.java:135)
... 23 more
{quote}
was (Author: adietish):
after fiddling for some time if have the slight impression that this is due to the
following:
We build a delegating progress monitor that holds references to the monitor of the job and
the monitor of the wizard dialog. This allows us to have subtasks reported to both (to the
status-bar in the workbench window and the wizard dialog).
When we call monitor#done, the progress monitor of the wizard dialog is already closed and
ends up in a SWTException "widget disposed" when the delegating monitor
delegates to the monitor of the wizard. That's at least how I would explain the
following execption I was able to catch:
{quote}org.eclipse.swt.SWTException: Failed to execute runnable
(org.eclipse.swt.SWTException: Widget is disposed)
at org.eclipse.swt.SWT.error(SWT.java:4282)
at org.eclipse.swt.SWT.error(SWT.java:4197)
at org.eclipse.swt.widgets.Synchronizer.runAsyncMessages(Synchronizer.java:138)
at org.eclipse.swt.widgets.Display.runAsyncMessages(Display.java:3563)
at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:3212)
at org.eclipse.ui.internal.Workbench.runEventLoop(Workbench.java:2696)
at org.eclipse.ui.internal.Workbench.runUI(Workbench.java:2660)
at org.eclipse.ui.internal.Workbench.access$4(Workbench.java:2494)
at org.eclipse.ui.internal.Workbench$7.run(Workbench.java:674)
at org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:332)
at org.eclipse.ui.internal.Workbench.createAndRunWorkbench(Workbench.java:667)
at org.eclipse.ui.PlatformUI.createAndRunWorkbench(PlatformUI.java:149)
at org.eclipse.ui.internal.ide.application.IDEApplication.start(IDEApplication.java:123)
at org.eclipse.equinox.internal.app.EclipseAppHandle.run(EclipseAppHandle.java:196)
at
org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.runApplication(EclipseAppLauncher.java:110)
at
org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.start(EclipseAppLauncher.java:79)
at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:344)
at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:179)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:597)
at org.eclipse.equinox.launcher.Main.invokeFramework(Main.java:622)
at org.eclipse.equinox.launcher.Main.basicRun(Main.java:577)
at org.eclipse.equinox.launcher.Main.run(Main.java:1410)
at org.eclipse.equinox.launcher.Main.main(Main.java:1386)
Caused by: org.eclipse.swt.SWTException: Widget is disposed
at org.eclipse.swt.SWT.error(SWT.java:4282)
at org.eclipse.swt.SWT.error(SWT.java:4197)
at org.eclipse.swt.SWT.error(SWT.java:4168)
at org.eclipse.swt.widgets.Widget.error(Widget.java:466)
at org.eclipse.swt.widgets.Widget.checkWidget(Widget.java:403)
at org.eclipse.swt.widgets.Label.setText(Label.java:571)
at org.eclipse.jface.wizard.ProgressMonitorPart.done(ProgressMonitorPart.java:184)
at
org.eclipse.jface.operation.AccumulatingProgressMonitor$2.run(AccumulatingProgressMonitor.java:163)
at org.eclipse.swt.widgets.RunnableLock.run(RunnableLock.java:35)
at org.eclipse.swt.widgets.Synchronizer.runAsyncMessages(Synchronizer.java:135)
... 23 more
{quote}
importing project into workspace.... stays around forever
---------------------------------------------------------
Key: JBIDE-10979
URL: https://issues.jboss.org/browse/JBIDE-10979
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: openshift
Reporter: Max Rydahl Andersen
Assignee: Max Rydahl Andersen
Priority: Blocker
Fix For: 3.3.0.Beta1
Attachments: dont-report-to-delegatingmonitor-in-wizardutils-2.patch,
dont-report-to-delegatingmonitor-in-wizardutils.patch
the progroess monitor seem to never get closed/finished in case of errors - could we get
those always closed in final block/wizard closing to avoid it always overriding any other
status updates
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
5:38 p.m.
[
https://issues.jboss.org/browse/JBIDE-10979?page=com.atlassian.jira.plugi...
]
Andre Dietisheim updated JBIDE-10979:
-------------------------------------
Attachment: dont-report-to-delegatingmonitor-in-wizardutils-3.patch
importing project into workspace.... stays around forever
---------------------------------------------------------
Key: JBIDE-10979
URL: https://issues.jboss.org/browse/JBIDE-10979
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: openshift
Reporter: Max Rydahl Andersen
Assignee: Max Rydahl Andersen
Priority: Blocker
Fix For: 3.3.0.Beta1
Attachments: dont-report-to-delegatingmonitor-in-wizardutils-2.patch,
dont-report-to-delegatingmonitor-in-wizardutils-3.patch,
dont-report-to-delegatingmonitor-in-wizardutils.patch
the progroess monitor seem to never get closed/finished in case of errors - could we get
those always closed in final block/wizard closing to avoid it always overriding any other
status updates
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
5:58 p.m.
[
https://issues.jboss.org/browse/JBIDE-10979?page=com.atlassian.jira.plugi...
]
Andre Dietisheim commented on JBIDE-10979:
------------------------------------------
committed to TRUNK (CR1) and BRANCH (Beta1)
importing project into workspace.... stays around forever
---------------------------------------------------------
Key: JBIDE-10979
URL: https://issues.jboss.org/browse/JBIDE-10979
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: openshift
Reporter: Max Rydahl Andersen
Assignee: Andre Dietisheim
Priority: Blocker
Fix For: 3.3.0.Beta1
Attachments: dont-report-to-delegatingmonitor-in-wizardutils-2.patch,
dont-report-to-delegatingmonitor-in-wizardutils-3.patch,
dont-report-to-delegatingmonitor-in-wizardutils.patch
the progroess monitor seem to never get closed/finished in case of errors - could we get
those always closed in final block/wizard closing to avoid it always overriding any other
status updates
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
3:12 a.m.
[
https://issues.jboss.org/browse/JBIDE-10979?page=com.atlassian.jira.plugi...
]
Andre Dietisheim resolved JBIDE-10979.
--------------------------------------
Resolution: Done
importing project into workspace.... stays around forever
---------------------------------------------------------
Key: JBIDE-10979
URL: https://issues.jboss.org/browse/JBIDE-10979
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: openshift
Reporter: Max Rydahl Andersen
Assignee: Andre Dietisheim
Priority: Blocker
Fix For: 3.3.0.Beta1
Attachments: dont-report-to-delegatingmonitor-in-wizardutils-2.patch,
dont-report-to-delegatingmonitor-in-wizardutils-3.patch,
dont-report-to-delegatingmonitor-in-wizardutils.patch
the progroess monitor seem to never get closed/finished in case of errors - could we get
those always closed in final block/wizard closing to avoid it always overriding any other
status updates
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
4:51 a.m.
[
https://issues.jboss.org/browse/JBIDE-10979?page=com.atlassian.jira.plugi...
]
Stefan Bunciak commented on JBIDE-10979:
----------------------------------------
@Andre: can you provide some method/scenario how to verify this issue? Thank you
importing project into workspace.... stays around forever
---------------------------------------------------------
Key: JBIDE-10979
URL: https://issues.jboss.org/browse/JBIDE-10979
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: openshift
Reporter: Max Rydahl Andersen
Assignee: Andre Dietisheim
Priority: Blocker
Fix For: 3.3.0.Beta1
Attachments: dont-report-to-delegatingmonitor-in-wizardutils-2.patch,
dont-report-to-delegatingmonitor-in-wizardutils-3.patch,
dont-report-to-delegatingmonitor-in-wizardutils.patch
the progroess monitor seem to never get closed/finished in case of errors - could we get
those always closed in final block/wizard closing to avoid it always overriding any other
status updates
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
5:03 a.m.
[
https://issues.jboss.org/browse/JBIDE-10979?page=com.atlassian.jira.plugi...
]
Andre Dietisheim commented on JBIDE-10979:
------------------------------------------
@Stefan: The only way to try to reproduce this is to import some OpenShift application to
your workspace. Then watch the status bar getting a progress bar and displaying the label
*Importing...*. Then see if that message is still displayed even when the progress monitor
and the job (look into the progress view if the Import job is done). If it is not, then
this issue is solved :) Otherwise it isn't :(
importing project into workspace.... stays around forever
---------------------------------------------------------
Key: JBIDE-10979
URL: https://issues.jboss.org/browse/JBIDE-10979
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: openshift
Reporter: Max Rydahl Andersen
Assignee: Andre Dietisheim
Priority: Blocker
Fix For: 3.3.0.Beta1
Attachments: dont-report-to-delegatingmonitor-in-wizardutils-2.patch,
dont-report-to-delegatingmonitor-in-wizardutils-3.patch,
dont-report-to-delegatingmonitor-in-wizardutils.patch
the progroess monitor seem to never get closed/finished in case of errors - could we get
those always closed in final block/wizard closing to avoid it always overriding any other
status updates
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
5:05 a.m.
[
https://issues.jboss.org/browse/JBIDE-10979?page=com.atlassian.jira.plugi...
]
Andre Dietisheim edited comment on JBIDE-10979 at 3/5/12 6:04 AM:
------------------------------------------------------------------
@Stefan: The only way to try to reproduce this is to import some OpenShift application to
your workspace. Look at the activity in the status bar of your Eclipse IDE. When the
import is executed, the status bar gets a progress bar and displays the label
*Importing...*. See if that message is still displayed when the job (look into the
progress view if the Import job is done) is done. If the status bar still displays
*Importing...* even if the import was executed (successfull case, error case) then this
issue is solved :) Otherwise it isn't :(
was (Author: adietish):
@Stefan: The only way to try to reproduce this is to import some OpenShift application
to your workspace. Look at the activity in the status bar of your Eclipse IDE. When the
import is executed, the status bar gets a progress bar and displaying the label
*Importing...*. Then see if that message is still displayed when the job (look into the
progress view if the Import job is done) is done. If the status bar still displays
*Importing...* even if the import was executed (successfull case, error case) then this
issue is solved :) Otherwise it isn't :(
importing project into workspace.... stays around forever
---------------------------------------------------------
Key: JBIDE-10979
URL: https://issues.jboss.org/browse/JBIDE-10979
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: openshift
Reporter: Max Rydahl Andersen
Assignee: Andre Dietisheim
Priority: Blocker
Fix For: 3.3.0.Beta1
Attachments: dont-report-to-delegatingmonitor-in-wizardutils-2.patch,
dont-report-to-delegatingmonitor-in-wizardutils-3.patch,
dont-report-to-delegatingmonitor-in-wizardutils.patch
the progroess monitor seem to never get closed/finished in case of errors - could we get
those always closed in final block/wizard closing to avoid it always overriding any other
status updates
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
5:05 a.m.
[
https://issues.jboss.org/browse/JBIDE-10979?page=com.atlassian.jira.plugi...
]
Andre Dietisheim edited comment on JBIDE-10979 at 3/5/12 6:03 AM:
------------------------------------------------------------------
@Stefan: The only way to try to reproduce this is to import some OpenShift application to
your workspace. Look at the activity in the status bar of your Eclipse IDE. When the
import is executed, the status bar gets a progress bar and displaying the label
*Importing...*. Then see if that message is still displayed when the job (look into the
progress view if the Import job is done) is done. If the status bar still displays
*Importing...* even if the import was executed (successfull case, error case) then this
issue is solved :) Otherwise it isn't :(
was (Author: adietish):
@Stefan: The only way to try to reproduce this is to import some OpenShift application
to your workspace. Then watch the status bar getting a progress bar and displaying the
label *Importing...*. Then see if that message is still displayed even when the progress
monitor and the job (look into the progress view if the Import job is done). If it is not,
then this issue is solved :) Otherwise it isn't :(
importing project into workspace.... stays around forever
---------------------------------------------------------
Key: JBIDE-10979
URL: https://issues.jboss.org/browse/JBIDE-10979
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: openshift
Reporter: Max Rydahl Andersen
Assignee: Andre Dietisheim
Priority: Blocker
Fix For: 3.3.0.Beta1
Attachments: dont-report-to-delegatingmonitor-in-wizardutils-2.patch,
dont-report-to-delegatingmonitor-in-wizardutils-3.patch,
dont-report-to-delegatingmonitor-in-wizardutils.patch
the progroess monitor seem to never get closed/finished in case of errors - could we get
those always closed in final block/wizard closing to avoid it always overriding any other
status updates
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
5:05 a.m.
[
https://issues.jboss.org/browse/JBIDE-10979?page=com.atlassian.jira.plugi...
]
Andre Dietisheim edited comment on JBIDE-10979 at 3/5/12 6:05 AM:
------------------------------------------------------------------
@Stefan: The only way to try to reproduce this is to import some OpenShift application to
your workspace. Look at the activity in the status bar of your Eclipse IDE. When the
import is executed, the status bar gets a progress bar and displays the label
*Importing...*. Check if that message is still displayed when the job (look into the
progress view if the Import job is done) is done. If the status bar still displays
*Importing...* even if the import is finished (successfull case, error case) then this
issue is solved :) Otherwise it isn't :(
was (Author: adietish):
@Stefan: The only way to try to reproduce this is to import some OpenShift application
to your workspace. Look at the activity in the status bar of your Eclipse IDE. When the
import is executed, the status bar gets a progress bar and displays the label
*Importing...*. See if that message is still displayed when the job (look into the
progress view if the Import job is done) is done. If the status bar still displays
*Importing...* even if the import was executed (successfull case, error case) then this
issue is solved :) Otherwise it isn't :(
importing project into workspace.... stays around forever
---------------------------------------------------------
Key: JBIDE-10979
URL: https://issues.jboss.org/browse/JBIDE-10979
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: openshift
Reporter: Max Rydahl Andersen
Assignee: Andre Dietisheim
Priority: Blocker
Fix For: 3.3.0.Beta1
Attachments: dont-report-to-delegatingmonitor-in-wizardutils-2.patch,
dont-report-to-delegatingmonitor-in-wizardutils-3.patch,
dont-report-to-delegatingmonitor-in-wizardutils.patch
the progroess monitor seem to never get closed/finished in case of errors - could we get
those always closed in final block/wizard closing to avoid it always overriding any other
status updates
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
5:10 a.m.
[
https://issues.jboss.org/browse/JBIDE-10979?page=com.atlassian.jira.plugi...
]
Max Rydahl Andersen commented on JBIDE-10979:
---------------------------------------------
to reproduce you need to trigger an error. i.e. use the wrong ssh key with the git repo or
have an existing project under the same name.
That was what caused it before. If no error occurs things goes fine, but if error occurs
things were not cleaned up.
importing project into workspace.... stays around forever
---------------------------------------------------------
Key: JBIDE-10979
URL: https://issues.jboss.org/browse/JBIDE-10979
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: openshift
Reporter: Max Rydahl Andersen
Assignee: Andre Dietisheim
Priority: Blocker
Fix For: 3.3.0.Beta1
Attachments: dont-report-to-delegatingmonitor-in-wizardutils-2.patch,
dont-report-to-delegatingmonitor-in-wizardutils-3.patch,
dont-report-to-delegatingmonitor-in-wizardutils.patch
the progroess monitor seem to never get closed/finished in case of errors - could we get
those always closed in final block/wizard closing to avoid it always overriding any other
status updates
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
6:49 a.m.
[
https://issues.jboss.org/browse/JBIDE-10979?page=com.atlassian.jira.plugi...
]
Andre Dietisheim commented on JBIDE-10979:
------------------------------------------
to me this happened always, not only when there was an error (see my comment here:
https://issues.jboss.org/secure/EditComment!default.jspa?id=12459661&...)
importing project into workspace.... stays around forever
---------------------------------------------------------
Key: JBIDE-10979
URL: https://issues.jboss.org/browse/JBIDE-10979
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: openshift
Reporter: Max Rydahl Andersen
Assignee: Andre Dietisheim
Priority: Blocker
Fix For: 3.3.0.Beta1
Attachments: dont-report-to-delegatingmonitor-in-wizardutils-2.patch,
dont-report-to-delegatingmonitor-in-wizardutils-3.patch,
dont-report-to-delegatingmonitor-in-wizardutils.patch
the progroess monitor seem to never get closed/finished in case of errors - could we get
those always closed in final block/wizard closing to avoid it always overriding any other
status updates
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
10:38 a.m.
[
https://issues.jboss.org/browse/JBIDE-10979?page=com.atlassian.jira.plugi...
]
Stefan Bunciak closed JBIDE-10979.
----------------------------------
Closing - could not reproduce it even 'Auth failed' error apperead during the
Application import proccess (used wrond ssh key). Label 'Importing' dissapeared
and progress bar finsihed.
Considering this as appropraite. Verified on JBoss Tools 3.3.0.Beta1c
importing project into workspace.... stays around forever
---------------------------------------------------------
Key: JBIDE-10979
URL: https://issues.jboss.org/browse/JBIDE-10979
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: openshift
Reporter: Max Rydahl Andersen
Assignee: Andre Dietisheim
Priority: Blocker
Fix For: 3.3.0.Beta1
Attachments: dont-report-to-delegatingmonitor-in-wizardutils-2.patch,
dont-report-to-delegatingmonitor-in-wizardutils-3.patch,
dont-report-to-delegatingmonitor-in-wizardutils.patch
the progroess monitor seem to never get closed/finished in case of errors - could we get
those always closed in final block/wizard closing to avoid it always overriding any other
status updates
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
5151
days inactive
5165
days old
jbosstools-issues@lists.jboss.org
19 comments
3 participants
participants (3)
-
Andre Dietisheim (JIRA) -
Max Rydahl Andersen (JIRA)
-
Stefan Bunciak (JIRA)