[JBoss JIRA] (ERT-245) SWTException below ContainerDataVolumeDialog$7$1.run (thrown in Widget.checkWidget) [EBZ#495518]
by Friendly Jira Robot (JIRA)
Friendly Jira Robot created ERT-245:
---------------------------------------
Summary: SWTException below ContainerDataVolumeDialog$7$1.run (thrown in Widget.checkWidget) [EBZ#495518]
Key: ERT-245
URL: https://issues.jboss.org/browse/ERT-245
Project: Eclipse Release Train
Issue Type: Task
Components: Linux Tools
Reporter: Friendly Jira Robot
Fix For: Neon (4.6)
The following problem was reported via the automated error reporting:
Message: Problems occurred when invoking code from plug-in: "org.eclipse.core.databinding.observable".
org.eclipse.swt.SWTException: Widget is disposed
at org.eclipse.swt.widgets.Widget.checkWidget(Widget.java:354)
at org.eclipse.swt.widgets.Control.setVisible(Control.java:3822)
at org.eclipse.linuxtools.internal.docker.ui.wizards.ContainerDataVolumeDialog$7$1.run(ContainerDataVolumeDialog.java:422)
at org.eclipse.swt.widgets.Synchronizer.syncExec(Synchronizer.java:186)
at org.eclipse.ui.internal.UISynchronizer.syncExec(UISynchronizer.java:145)
at org.eclipse.swt.widgets.Display.syncExec(Display.java:4761)
at org.eclipse.linuxtools.internal.docker.ui.wizards.ContainerDataVolumeDialog$7.handleChange(ContainerDataVolumeDialog.java:413)
at org.eclipse.core.databinding.observable.ChangeEvent.dispatch(ChangeEvent.java:42)
at org.eclipse.core.databinding.observable.ChangeManager.fireEvent(ChangeManager.java:119)
at org.eclipse.core.databinding.observable.AbstractObservable.fireChange(AbstractObservable.java:71)
at org.eclipse.core.databinding.observable.value.DecoratingObservableValue.fireValueChange(DecoratingObservableValue.java:56)
at org.eclipse.core.databinding.observable.value.DecoratingObservableValue.handleValueChange(DecoratingObservableValue.java:99)
at org.eclipse.core.databinding.observable.value.DecoratingObservableValue$1.handleValueChange(DecoratingObservableValue.java:72)
at org.eclipse.core.databinding.observable.value.ValueChangeEvent.dispatch(ValueChangeEvent.java:63)
at org.eclipse.core.databinding.observable.ChangeManager.fireEvent(ChangeManager.java:119)
at org.eclipse.core.databinding.observable.value.AbstractObservableValue.fireValueChange(AbstractObservableValue.java:74)
at org.eclipse.core.internal.databinding.property.value.SimplePropertyObservableValue.notifyIfChanged(SimplePropertyObservableValue.java:127)
at org.eclipse.core.internal.databinding.property.value.SimplePropertyObservableValue.access$2(SimplePropertyObservableValue.java:119)
at org.eclipse.core.internal.databinding.property.value.SimplePropertyObservableValue$1$1.run(SimplePropertyObservableValue.java:69)
at org.eclipse.core.databinding.observable.Realm$1.run(Realm.java:150)
at org.eclipse.core.runtime.SafeRunner.run(SafeRunner.java:42)
at org.eclipse.core.databinding.observable.Realm.safeRun(Realm.java:154)
at org.eclipse.core.databinding.observable.Realm.exec(Realm.java:172)
at org.eclipse.core.internal.databinding.property.value.SimplePropertyObservableValue$1.handleEvent(SimplePropertyObservableValue.java:65)
at org.eclipse.core.databinding.property.NativePropertyListener.fireChange(NativePropertyListener.java:65)
at org.eclipse.core.internal.databinding.beans.BeanPropertyListener.propertyChange(BeanPropertyListener.java:50)
at java.beans.PropertyChangeSupport.fire(null:-1)
at java.beans.PropertyChangeSupport.firePropertyChange(null:-1)
at java.beans.PropertyChangeSupport.firePropertyChange(null:-1)
at org.eclipse.linuxtools.internal.docker.ui.databinding.BaseDatabindingModel.firePropertyChange(BaseDatabindingModel.java:42)
at org.eclipse.linuxtools.internal.docker.ui.wizards.DataVolumeModel.setHostPathMount(DataVolumeModel.java:221)
at org.eclipse.linuxtools.internal.docker.ui.launch.RunImageVolumesTab$4.widgetSelected(RunImageVolumesTab.java:295)
at org.eclipse.swt.widgets.TypedListener.handleEvent(TypedListener.java:248)
at org.eclipse.swt.widgets.EventTable.sendEvent(EventTable.java:84)
Bundles:
| org.eclipse.core.databinding.beans | 1.3.0.v20150422-0725 | 1.3.0.v20150422-0725 |
| org.eclipse.core.databinding.observable | 1.5.0.v20150422-0725 | 1.5.0.v20150422-0725 |
| org.eclipse.core.databinding.property | 1.5.0.v20150422-0725 | 1.5.0.v20150422-0725 |
| org.eclipse.core.runtime | 3.11.1.v20150903-1804 | 3.11.1.v20150903-1804 |
| org.eclipse.linuxtools.docker.ui | 1.2.0.201512112123 | 1.2.0.201512112123 |
| org.eclipse.swt | 3.104.2.v20160212-1350 | 3.104.2.v20160212-1350 |
| org.eclipse.ui | 3.107.0.v20150507-1945 | 3.107.0.v20150507-1945 |
Operating Systems:
| Windows | 6.1.0 | 6.1.0 |
The above information is a snapshot of the collected data. Visit https://dev.eclipse.org/recommenders/committers/aeri/v2/#!/problems/574ee... for the latest data.
Thank you for your assistance.
Your friendly error-reports-inbox.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 10 months
[JBoss JIRA] (ERT-244) NullPointerException in ContainerDataVolumeDialog.setOkButtonEnabled [EBZ#495517]
by Friendly Jira Robot (JIRA)
Friendly Jira Robot created ERT-244:
---------------------------------------
Summary: NullPointerException in ContainerDataVolumeDialog.setOkButtonEnabled [EBZ#495517]
Key: ERT-244
URL: https://issues.jboss.org/browse/ERT-244
Project: Eclipse Release Train
Issue Type: Task
Components: Linux Tools
Reporter: Friendly Jira Robot
Fix For: Neon (4.6)
The following problem was reported via the automated error reporting:
Message: Problems occurred when invoking code from plug-in: "org.eclipse.core.databinding.observable".
java.lang.NullPointerException: null
at org.eclipse.linuxtools.internal.docker.ui.wizards.ContainerDataVolumeDialog.setOkButtonEnabled(ContainerDataVolumeDialog.java:483)
at org.eclipse.linuxtools.internal.docker.ui.wizards.ContainerDataVolumeDialog.access$2(ContainerDataVolumeDialog.java:482)
at org.eclipse.linuxtools.internal.docker.ui.wizards.ContainerDataVolumeDialog$7$1.run(ContainerDataVolumeDialog.java:438)
at org.eclipse.swt.widgets.Synchronizer.syncExec(Synchronizer.java:186)
at org.eclipse.ui.internal.UISynchronizer.syncExec(UISynchronizer.java:145)
at org.eclipse.swt.widgets.Display.syncExec(Display.java:4761)
at org.eclipse.linuxtools.internal.docker.ui.wizards.ContainerDataVolumeDialog$7.handleChange(ContainerDataVolumeDialog.java:413)
at org.eclipse.core.databinding.observable.ChangeEvent.dispatch(ChangeEvent.java:42)
at org.eclipse.core.databinding.observable.ChangeManager.fireEvent(ChangeManager.java:119)
at org.eclipse.core.databinding.observable.AbstractObservable.fireChange(AbstractObservable.java:71)
at org.eclipse.core.databinding.observable.value.DecoratingObservableValue.fireValueChange(DecoratingObservableValue.java:56)
at org.eclipse.core.databinding.observable.value.DecoratingObservableValue.handleValueChange(DecoratingObservableValue.java:99)
at org.eclipse.core.databinding.observable.value.DecoratingObservableValue$1.handleValueChange(DecoratingObservableValue.java:72)
at org.eclipse.core.databinding.observable.value.ValueChangeEvent.dispatch(ValueChangeEvent.java:63)
at org.eclipse.core.databinding.observable.ChangeManager.fireEvent(ChangeManager.java:119)
at org.eclipse.core.databinding.observable.value.AbstractObservableValue.fireValueChange(AbstractObservableValue.java:74)
at org.eclipse.core.internal.databinding.property.value.SimplePropertyObservableValue.notifyIfChanged(SimplePropertyObservableValue.java:127)
at org.eclipse.core.internal.databinding.property.value.SimplePropertyObservableValue.access$2(SimplePropertyObservableValue.java:119)
at org.eclipse.core.internal.databinding.property.value.SimplePropertyObservableValue$1$1.run(SimplePropertyObservableValue.java:69)
at org.eclipse.core.databinding.observable.Realm$1.run(Realm.java:150)
at org.eclipse.core.runtime.SafeRunner.run(SafeRunner.java:42)
at org.eclipse.core.databinding.observable.Realm.safeRun(Realm.java:154)
at org.eclipse.core.databinding.observable.Realm.exec(Realm.java:172)
at org.eclipse.core.internal.databinding.property.value.SimplePropertyObservableValue$1.handleEvent(SimplePropertyObservableValue.java:65)
at org.eclipse.core.databinding.property.NativePropertyListener.fireChange(NativePropertyListener.java:65)
at org.eclipse.core.internal.databinding.beans.BeanPropertyListener.propertyChange(BeanPropertyListener.java:50)
at java.beans.PropertyChangeSupport.fire(null:-1)
at java.beans.PropertyChangeSupport.firePropertyChange(null:-1)
at java.beans.PropertyChangeSupport.firePropertyChange(null:-1)
at org.eclipse.linuxtools.internal.docker.ui.databinding.BaseDatabindingModel.firePropertyChange(BaseDatabindingModel.java:42)
at org.eclipse.linuxtools.internal.docker.ui.wizards.DataVolumeModel.setMountType(DataVolumeModel.java:208)
at org.eclipse.linuxtools.internal.docker.ui.launch.RunImageVolumesTab$4.widgetSelected(RunImageVolumesTab.java:294)
at org.eclipse.swt.widgets.TypedListener.handleEvent(TypedListener.java:248)
at org.eclipse.swt.widgets.EventTable.sendEvent(EventTable.java:84)
Bundles:
| org.eclipse.core.databinding.beans | 1.3.0.v20150422-0725 | 1.3.0.v20150422-0725 |
| org.eclipse.core.databinding.observable | 1.5.0.v20150422-0725 | 1.5.0.v20150422-0725 |
| org.eclipse.core.databinding.property | 1.5.0.v20150422-0725 | 1.5.0.v20150422-0725 |
| org.eclipse.core.runtime | 3.11.1.v20150903-1804 | 3.11.1.v20150903-1804 |
| org.eclipse.linuxtools.docker.ui | 1.2.0.201512112123 | 1.2.0.201512112123 |
| org.eclipse.swt | 3.104.2.v20160212-1350 | 3.104.2.v20160212-1350 |
| org.eclipse.ui | 3.107.0.v20150507-1945 | 3.107.0.v20150507-1945 |
Operating Systems:
| Windows | 6.1.0 | 6.1.0 |
The above information is a snapshot of the collected data. Visit https://dev.eclipse.org/recommenders/committers/aeri/v2/#!/problems/574ee... for the latest data.
Thank you for your assistance.
Your friendly error-reports-inbox.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 10 months
[JBoss JIRA] (JBIDE-22544) Redudant error report in Devstudio's Problems View
by Ondrej Dockal (JIRA)
Ondrej Dockal created JBIDE-22544:
-------------------------------------
Summary: Redudant error report in Devstudio's Problems View
Key: JBIDE-22544
URL: https://issues.jboss.org/browse/JBIDE-22544
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: batch
Reporter: Ondrej Dockal
Attachments: org.jboss.tools.batch.ui.bot.test.editor.design.DesignChunkStepElementTest.createStep(7).png
Some test fails on checking number of errors in Problems View in devstudio. There are duplicated error reports.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 10 months
[JBoss JIRA] (JBIDE-22241) OpenShift Explorer: Cascade resource deletion
by Marián Labuda (JIRA)
[ https://issues.jboss.org/browse/JBIDE-22241?page=com.atlassian.jira.plugi... ]
Marián Labuda commented on JBIDE-22241:
---------------------------------------
Yeah, at the moment once you delete a service via oc, routing stays alive, but oc status give you an error:
{code}Errors:
* route/eap-app is routing traffic to svc/eap-app, but either the administrator has not installed a router or the router is not selecting this route.{code}
and I think this is not something users would like to have.
> OpenShift Explorer: Cascade resource deletion
> ---------------------------------------------
>
> Key: JBIDE-22241
> URL: https://issues.jboss.org/browse/JBIDE-22241
> Project: Tools (JBoss Tools)
> Issue Type: Enhancement
> Components: openshift
> Affects Versions: 4.4.0.Alpha1
> Reporter: Marián Labuda
> Assignee: Jeff MAURY
> Labels: explorer, openshift_v3, ux
> Fix For: 4.4.1.Alpha1
>
>
> It would be nice to have a possibility to allow cascading deletion, deletion of related resource/resource managed by the resource which is about to be deleted.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 10 months
[JBoss JIRA] (JBIDE-21958) Provide filters by status on Problems view
by Marcel Bruch (JIRA)
[ https://issues.jboss.org/browse/JBIDE-21958?page=com.atlassian.jira.plugi... ]
Marcel Bruch closed JBIDE-21958.
--------------------------------
Fix Version/s: 4.4.x
Resolution: Done
The all-problems-view now allows filtering of problems based on different criteria, e.g, linked to bug tracker yes/no, resolutions, status, severity etc.
> Provide filters by status on Problems view
> -------------------------------------------
>
> Key: JBIDE-21958
> URL: https://issues.jboss.org/browse/JBIDE-21958
> Project: Tools (JBoss Tools)
> Issue Type: Feature Request
> Components: aeri
> Reporter: Aurélien Pupier
> Priority: Minor
> Fix For: 4.4.x
>
>
> Specific use case I have in mind:
> - have the list of pending reports
> - have the list of pending reports with no issue
> If we can filter on every field it would be nice too but perhaps as a second iteration
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 10 months
[JBoss JIRA] (JBIDE-22418) Update AERI Eclipse IDE Client to 2.0
by Marcel Bruch (JIRA)
[ https://issues.jboss.org/browse/JBIDE-22418?page=com.atlassian.jira.plugi... ]
Marcel Bruch commented on JBIDE-22418:
--------------------------------------
Assigning this to Nick to get his attention.
Milestones and Stable update site contain 2.0.x now. Both can be used as drop-in replacement. No major code changes since 1.100. There is no Neon specific code in 2.0.x anymore since EF withdrawed sending the eclipse.uuid per request.
> Update AERI Eclipse IDE Client to 2.0
> -------------------------------------
>
> Key: JBIDE-22418
> URL: https://issues.jboss.org/browse/JBIDE-22418
> Project: Tools (JBoss Tools)
> Issue Type: Feature Request
> Components: aeri
> Reporter: Marcel Bruch
> Assignee: Nick Boldt
>
> I'm about to release 2.0.0 for Neon.0.
> [~nickboldt], what is the earliest release of JBIDE / Devstudio that will pick up 2.0.0?
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 10 months
[JBoss JIRA] (JBIDE-21723) debug/warning errors from aeri in logs
by Marcel Bruch (JIRA)
[ https://issues.jboss.org/browse/JBIDE-21723?page=com.atlassian.jira.plugi... ]
Marcel Bruch closed JBIDE-21723.
--------------------------------
Resolution: Done
Fixed on eclipse side
> debug/warning errors from aeri in logs
> --------------------------------------
>
> Key: JBIDE-21723
> URL: https://issues.jboss.org/browse/JBIDE-21723
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: aeri
> Reporter: Max Rydahl Andersen
>
> seeing a info and warning message when errors occurs.
> {code}
> eclipse.buildId=4.6.0.I20151209-2300
> java.version=1.8.0_20
> java.vendor=Oracle Corporation
> BootLoader constants: OS=macosx, ARCH=x86_64, WS=cocoa, NL=en_US
> Framework arguments: -product org.eclipse.epp.package.jee.product -product org.eclipse.epp.package.jee.product -keyring /Users/max/.eclipse_keyring
> Command-line arguments: -os macosx -ws cocoa -arch x86_64 -product org.eclipse.epp.package.jee.product -data file:/Users/max/workspaces/eclipseerror/ -product org.eclipse.epp.package.jee.product -keyring /Users/max/.eclipse_keyring
> org.eclipse.epp.logging.aeri.ide
> Info
> Fri Feb 19 18:56:42 CET 2016
> Added ‘Unknown category 'org.jboss.to…8.jar_5289305038018513896.jar’ under ‘b2c2e18436026b0d358c3d135c923fc4’ to local history at /Users/max/workspaces/eclipsee…org.jboss.tools/local-history. ; version: 1.100.0.v20160203-1727
> org.eclipse.epp.logging.aeri.core.util.Logs$LogTraceException
> at org.eclipse.epp.logging.aeri.core.util.Logs$LogTraceException.newTrace(Logs.java:383)
> at org.eclipse.epp.logging.aeri.core.util.Logs.log(Logs.java:134)
> at org.eclipse.epp.internal.logging.aeri.ide.server.LocalReportsHistory.doRemember(LocalReportsHistory.java:137)
> at org.eclipse.epp.internal.logging.aeri.ide.server.LocalReportsHistory.remember(LocalReportsHistory.java:119)
> at org.eclipse.epp.internal.logging.aeri.ide.server.mars.ServerConnection.submit(ServerConnection.java:190)
> at org.eclipse.epp.internal.logging.aeri.ide.utils.UploadReportsScheduler.send(UploadReportsScheduler.java:52)
> at org.eclipse.epp.internal.logging.aeri.ide.utils.UploadReportsScheduler.send(UploadReportsScheduler.java:69)
> at org.eclipse.epp.internal.logging.aeri.ide.IDEStartup$2.send(IDEStartup.java:98)
> at org.eclipse.epp.internal.logging.aeri.ide.utils.UploadReportsScheduler$UploadJob.run(UploadReportsScheduler.java:106)
> at org.eclipse.core.internal.jobs.Worker.run(Worker.java:55)
> {code}
> and
> {code}
> eclipse.buildId=4.6.0.I20151209-2300
> java.version=1.8.0_20
> java.vendor=Oracle Corporation
> BootLoader constants: OS=macosx, ARCH=x86_64, WS=cocoa, NL=en_US
> Framework arguments: -product org.eclipse.epp.package.jee.product -product org.eclipse.epp.package.jee.product -keyring /Users/max/.eclipse_keyring
> Command-line arguments: -os macosx -ws cocoa -arch x86_64 -product org.eclipse.epp.package.jee.product -data file:/Users/max/workspaces/eclipseerror/ -product org.eclipse.epp.package.jee.product -keyring /Users/max/.eclipse_keyring
> org.eclipse.epp.logging.aeri.ide
> Warning
> Fri Feb 19 18:56:42 CET 2016
> Unexpected response : UNKNOWN ‐ UNKNOWN ; version: 1.100.0.v20160203-1727
> org.eclipse.epp.logging.aeri.core.util.Logs$LogTraceException
> at org.eclipse.epp.logging.aeri.core.util.Logs$LogTraceException.newTrace(Logs.java:383)
> at org.eclipse.epp.logging.aeri.core.util.Logs.log(Logs.java:134)
> at org.eclipse.epp.internal.logging.aeri.ide.server.mars.IO.tryParse(IO.java:237)
> at org.eclipse.epp.internal.logging.aeri.ide.server.mars.IO.upload(IO.java:116)
> at org.eclipse.epp.internal.logging.aeri.ide.server.mars.ServerConnection.submit(ServerConnection.java:189)
> at org.eclipse.epp.internal.logging.aeri.ide.utils.UploadReportsScheduler.send(UploadReportsScheduler.java:52)
> at org.eclipse.epp.internal.logging.aeri.ide.utils.UploadReportsScheduler.send(UploadReportsScheduler.java:69)
> at org.eclipse.epp.internal.logging.aeri.ide.IDEStartup$2.send(IDEStartup.java:98)
> at org.eclipse.epp.internal.logging.aeri.ide.utils.UploadReportsScheduler$UploadJob.run(UploadReportsScheduler.java:106)
> at org.eclipse.core.internal.jobs.Worker.run(Worker.java:55)
> {code}
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 10 months