[JBoss JIRA] (ERT-463) DockerException in DockerExplorerContentProvider$1.run [EBZ#508266]
by Friendly Jira Robot (JIRA)
Friendly Jira Robot created ERT-463:
---------------------------------------
Summary: DockerException in DockerExplorerContentProvider$1.run [EBZ#508266]
Key: ERT-463
URL: https://issues.jboss.org/browse/ERT-463
Project: Eclipse Release Train
Issue Type: Task
Components: Linux Tools
Reporter: Friendly Jira Robot
The following problem was reported via the automated error reporting:
Message: HIDDEN
org.eclipse.linuxtools.docker.core.DockerException: HIDDEN
at org.eclipse.linuxtools.internal.docker.ui.views.DockerExplorerContentProvider$1.run(DockerExplorerContentProvider.java:186)
at org.eclipse.core.internal.jobs.Worker.run(Worker.java:55)
Bundles:
| org.eclipse.core.jobs | 3.8.0.v20160509-0411 | 3.8.0.v20160509-0411 |
| org.eclipse.linuxtools.docker.ui | 2.1.0.201611050402 | 2.1.0.201611050402 |
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/5836a... for the latest data.
Thank you for your assistance.
Your friendly error-reports-inbox.
Created on behalf of xcoulon(a)xxxxxx.xxx
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
9 years, 4 months
[JBoss JIRA] (ERT-461) NullPointerException when the list of images for the connection to use to run an image is null [EBZ#507769]
by Xavier Coulon (JIRA)
[ https://issues.jboss.org/browse/ERT-461?page=com.atlassian.jira.plugin.sy... ]
Xavier Coulon reassigned ERT-461:
---------------------------------
Issue Type: Bug (was: Task)
Sprint: devex #123 November 2016
Affects Version/s: Neon (4.6)
Assignee: Xavier Coulon
> NullPointerException when the list of images for the connection to use to run an image is null [EBZ#507769]
> -----------------------------------------------------------------------------------------------------------
>
> Key: ERT-461
> URL: https://issues.jboss.org/browse/ERT-461
> Project: Eclipse Release Train
> Issue Type: Bug
> Components: Linux Tools
> Affects Versions: Neon (4.6)
> Reporter: Friendly Jira Robot
> Assignee: Xavier Coulon
> Labels: 5.2.0, Docker, bzira
> Fix For: Neon.2 (4.6)
>
>
> Here's the stacktrace:
> java.lang.NullPointerException
> at org.eclipse.linuxtools.internal.docker.ui.wizards.ImageRunSelectionModel.refreshImageNames(ImageRunSelectionModel.java:131)
> at org.eclipse.linuxtools.internal.docker.ui.wizards.ImageRunSelectionModel.setSelectedConnectionName(ImageRunSelectionModel.java:182)
> at org.eclipse.linuxtools.internal.docker.ui.launch.RunImageMainTab.initializeFrom(RunImageMainTab.java:503)
> at org.eclipse.debug.ui.AbstractLaunchConfigurationTabGroup.initializeFrom(AbstractLaunchConfigurationTabGroup.java:90)
> at org.eclipse.debug.internal.ui.launchConfigurations.LaunchConfigurationTabGroupWrapper.initializeFrom(LaunchConfigurationTabGroupWrapper.java:201)
> at org.eclipse.debug.internal.ui.launchConfigurations.LaunchConfigurationTabGroupViewer.displayInstanceTabs(LaunchConfigurationTabGroupViewer.java:766)
> at org.eclipse.debug.internal.ui.launchConfigurations.LaunchConfigurationTabGroupViewer$8.run(LaunchConfigurationTabGroupViewer.java:637)
> at org.eclipse.swt.custom.BusyIndicator.showWhile(BusyIndicator.java:70)
> at org.eclipse.debug.internal.ui.launchConfigurations.LaunchConfigurationTabGroupViewer.inputChanged(LaunchConfigurationTabGroupViewer.java:654)
> at org.eclipse.debug.internal.ui.launchConfigurations.LaunchConfigurationTabGroupViewer.setInput0(LaunchConfigurationTabGroupViewer.java:615)
> at org.eclipse.debug.internal.ui.launchConfigurations.LaunchConfigurationTabGroupViewer.setInput(LaunchConfigurationTabGroupViewer.java:590)
> at org.eclipse.debug.internal.ui.launchConfigurations.LaunchConfigurationsDialog.handleLaunchConfigurationSelectionChanged(LaunchConfigurationsDialog.java:1008)
> at org.eclipse.debug.internal.ui.launchConfigurations.LaunchConfigurationsDialog$4.selectionChanged(LaunchConfigurationsDialog.java:621)
> at org.eclipse.jface.viewers.StructuredViewer$3.run(StructuredViewer.java:878)
> at org.eclipse.core.runtime.SafeRunner.run(SafeRunner.java:42)
> at org.eclipse.ui.internal.JFaceUtil$1.run(JFaceUtil.java:50)
> at org.eclipse.jface.util.SafeRunnable.run(SafeRunnable.java:173)
> at org.eclipse.jface.viewers.StructuredViewer.firePostSelectionChanged(StructuredViewer.java:875)
> at org.eclipse.jface.viewers.StructuredViewer.handlePostSelect(StructuredViewer.java:1244)
> at org.eclipse.jface.viewers.StructuredViewer$5.widgetSelected(StructuredViewer.java:1270)
> at org.eclipse.jface.util.OpenStrategy.firePostSelectionEvent(OpenStrategy.java:265)
> at org.eclipse.jface.util.OpenStrategy.access$5(OpenStrategy.java:259)
> at org.eclipse.jface.util.OpenStrategy$1.lambda$1(OpenStrategy.java:431)
> at org.eclipse.jface.util.OpenStrategy$1$$Lambda$79/1410723144.run(Unknown Source)
> at org.eclipse.swt.widgets.RunnableLock.run(RunnableLock.java:35)
> at org.eclipse.swt.widgets.Synchronizer.runAsyncMessages(Synchronizer.java:182)
> at org.eclipse.swt.widgets.Display.runAsyncMessages(Display.java:4024)
> at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:3700)
> at org.eclipse.jface.window.Window.runEventLoop(Window.java:818)
> at org.eclipse.jface.window.Window.open(Window.java:794)
> at org.eclipse.debug.internal.ui.launchConfigurations.LaunchConfigurationsDialog.open(LaunchConfigurationsDialog.java:1203)
> at org.eclipse.debug.ui.DebugUITools$3.run(DebugUITools.java:629)
> at org.eclipse.swt.custom.BusyIndicator.showWhile(BusyIndicator.java:70)
> at org.eclipse.debug.ui.DebugUITools.openLaunchConfigurationDialogOnGroup(DebugUITools.java:637)
> at org.eclipse.debug.ui.DebugUITools.openLaunchConfigurationDialogOnGroup(DebugUITools.java:570)
> at org.eclipse.debug.ui.actions.OpenLaunchDialogAction.run(OpenLaunchDialogAction.java:82)
> at org.eclipse.jface.action.Action.runWithEvent(Action.java:473)
> at org.eclipse.jface.action.ActionContributionItem.handleWidgetSelection(ActionContributionItem.java:565)
> at org.eclipse.jface.action.ActionContributionItem.lambda$4(ActionContributionItem.java:397)
> at org.eclipse.jface.action.ActionContributionItem$$Lambda$36/899869274.handleEvent(Unknown Source)
> at org.eclipse.swt.widgets.EventTable.sendEvent(EventTable.java:84)
> at org.eclipse.swt.widgets.Display.sendEvent(Display.java:4248)
> at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1501)
> at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1524)
> at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1509)
> at org.eclipse.swt.widgets.Widget.notifyListeners(Widget.java:1313)
> at org.eclipse.swt.widgets.Display.runDeferredEvents(Display.java:4072)
> at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:3698)
> at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine$4.run(PartRenderingEngine.java:1121)
> at org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:336)
> at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine.run(PartRenderingEngine.java:1022)
> at org.eclipse.e4.ui.internal.workbench.E4Workbench.createAndRunUI(E4Workbench.java:150)
> at org.eclipse.ui.internal.Workbench$5.run(Workbench.java:687)
> at org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:336)
> at org.eclipse.ui.internal.Workbench.createAndRunWorkbench(Workbench.java:604)
> at org.eclipse.ui.PlatformUI.createAndRunWorkbench(PlatformUI.java:148)
> at org.eclipse.ui.internal.ide.application.IDEApplication.start(IDEApplication.java:138)
> at org.eclipse.equinox.internal.app.EclipseAppHandle.run(EclipseAppHandle.java:196)
> at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.runApplication(EclipseAppLauncher.java:134)
> at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.start(EclipseAppLauncher.java:104)
> at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:388)
> at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:243)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
> at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> at java.lang.reflect.Method.invoke(Method.java:497)
> at org.eclipse.equinox.launcher.Main.invokeFramework(Main.java:673)
> at org.eclipse.equinox.launcher.Main.basicRun(Main.java:610)
> at org.eclipse.equinox.launcher.Main.run(Main.java:1519)
> at org.eclipse.equinox.launcher.Main.main(Main.java:1492)
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
9 years, 4 months
[JBoss JIRA] (ERT-460) Launch configuration for running images cannot be saved as shared file [EBZ#507765]
by Xavier Coulon (JIRA)
[ https://issues.jboss.org/browse/ERT-460?page=com.atlassian.jira.plugin.sy... ]
Xavier Coulon reassigned ERT-460:
---------------------------------
Issue Type: Enhancement (was: Task)
Sprint: devex #123 November 2016
Affects Version/s: Neon.1 (4.6)
Assignee: Xavier Coulon
> Launch configuration for running images cannot be saved as shared file [EBZ#507765]
> -----------------------------------------------------------------------------------
>
> Key: ERT-460
> URL: https://issues.jboss.org/browse/ERT-460
> Project: Eclipse Release Train
> Issue Type: Enhancement
> Components: Linux Tools
> Affects Versions: Neon.1 (4.6)
> Reporter: Friendly Jira Robot
> Assignee: Xavier Coulon
> Priority: Trivial
> Labels: 5.2.0, Docker, bzira
> Fix For: Neon.2 (4.6)
>
>
> The "Run Docker Image" launch configuration unfortunately cannot be saved to a shared file. The launch configuration types "Docker Compose" and "Build Docker Image" both support this via their respective "Common" tab.
> It would be great to have the same support for the "Run Docker Image" launch configurations. This way configurations can be checked into version control and easily shared between team members.
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
9 years, 4 months
[JBoss JIRA] (ERT-459) Report docker-compose error when the process failed to start [EBZ#506262]
by Xavier Coulon (JIRA)
[ https://issues.jboss.org/browse/ERT-459?page=com.atlassian.jira.plugin.sy... ]
Xavier Coulon reassigned ERT-459:
---------------------------------
Issue Type: Bug (was: Task)
Sprint: devex #123 November 2016
Affects Version/s: Neon.1 (4.6)
Assignee: Xavier Coulon
> Report docker-compose error when the process failed to start [EBZ#506262]
> -------------------------------------------------------------------------
>
> Key: ERT-459
> URL: https://issues.jboss.org/browse/ERT-459
> Project: Eclipse Release Train
> Issue Type: Bug
> Components: Linux Tools
> Affects Versions: Neon.1 (4.6)
> Reporter: Friendly Jira Robot
> Assignee: Xavier Coulon
> Labels: 5.2.0, Docker, bzira
> Fix For: Neon.2 (4.6)
>
>
> For now, the only thing that the user can see is an entry in the "Error Log" view, but with no details on what happened. Eg: "'docker-compose up' exited with code 1".
> We should display an error dialog with the real error, such as:
> "The Compose file './docker-compose.yml' is invalid because:
> services.app.links contains an invalid type, it should be an array"
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
9 years, 4 months
[JBoss JIRA] (JBIDE-23352) Deploy Docker Wizard: Default routing port selection need more info for users
by Marián Labuda (JIRA)
[ https://issues.jboss.org/browse/JBIDE-23352?page=com.atlassian.jira.plugi... ]
Marián Labuda closed JBIDE-23352.
---------------------------------
Verified in DevStudio 10.2.0.GA Build id: GA-v20161125-1418-B55.
> Deploy Docker Wizard: Default routing port selection need more info for users
> -----------------------------------------------------------------------------
>
> Key: JBIDE-23352
> URL: https://issues.jboss.org/browse/JBIDE-23352
> Project: Tools (JBoss Tools)
> Issue Type: Enhancement
> Components: openshift
> Affects Versions: 4.4.1.AM2
> Reporter: Marián Labuda
> Assignee: Jeff MAURY
> Labels: deploy_docker_wizard, openshift_v3
> Fix For: 4.4.2.Final
>
> Attachments: no_route_selected.png, refdoc-services-1.png, refdoc-services-2.png, webui-deploy-docker-image.png
>
>
> In the wizard on wizard page Services & Routing Settings, there is a table with mapped ports. No port is selected by default , but OpenShift knows what to open.
> If there is only one port mapping, we could check it by default. If there are more port mappings, we could show a label/info/description what is gonna be done under the hood, so users will know what is happening.
> steps to reproduce:
> # EXEC: In Docker Explroer: pick an image and choose "Deploy to OpenShift..." in the context menu
> # EXEC: get to the "Services & Routing Settings" page
> !no_route_selected.png!
> It's not obvious to the user what the wizard will create: A service that "exposes" pod ports and a route that points to this service. Furthermore it's not obvious that without a "checked" (used by route) port, the route will round-robin through the available ports. Additionally we should show the user what ports are exposed by the pod, and which ones are ports that the user added while no explicit exposure is defined in the pod (so he's on his own, if there's nothing listening on them he'll have users face non-functional or no reposonses at all).
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
9 years, 4 months
[JBoss JIRA] (JBIDE-21857) Hot class reload doesn't work on OpenShift
by Marián Labuda (JIRA)
[ https://issues.jboss.org/browse/JBIDE-21857?page=com.atlassian.jira.plugi... ]
Marián Labuda commented on JBIDE-21857:
---------------------------------------
So what precisely is working? I though with JMX connected to OpenShift there would be triggered GC and some magic around to allow e.g. adding a new methods to classes... Debugging in old way did work. Bcs. this bug JIRA has title "HCR doesnt work on OpenShift" and is resolved as done.
> Hot class reload doesn't work on OpenShift
> ------------------------------------------
>
> Key: JBIDE-21857
> URL: https://issues.jboss.org/browse/JBIDE-21857
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: openshift
> Affects Versions: 4.3.1.Beta2
> Reporter: Fred Bricon
> Assignee: Rob Stryker
> Fix For: 4.4.2.Final, 4.4.3.AM1, 4.5.0.AM1
>
> Attachments: HCRFailure.zip
>
>
> When enabling debug mode on an EAP server deployed on OpenShift, locally changing a class file will :
> - work sometimes when only the content of the method changed, but could fail in some other occasions with the Debugger saying the JDK is out of sync
> - will always fail if a method signature changed, the debugger saying JDK is out of sync
> Restarting the deployed module (with the .dodeploy flag) doesn't fixes the issue (as opposed to the same tweak ahen running on a local EAP server)
> This may be caused by running OpenJDK? Does it support the same level of debugging as Oracle JDK?
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
9 years, 4 months
[JBoss JIRA] (JBIDE-21857) Hot class reload doesn't work on OpenShift
by Marián Labuda (JIRA)
[ https://issues.jboss.org/browse/JBIDE-21857?page=com.atlassian.jira.plugi... ]
Marián Labuda edited comment on JBIDE-21857 at 11/28/16 3:48 AM:
-----------------------------------------------------------------
So what precisely has been done there and should work? I though with JMX connected to OpenShift there would be triggered GC and some magic around to allow e.g. adding a new methods to classes... Debugging in old way did work. Bcs. this bug JIRA has title "HCR doesnt work on OpenShift" and is resolved as done.
was (Author: mlabuda):
So what precisely is working? I though with JMX connected to OpenShift there would be triggered GC and some magic around to allow e.g. adding a new methods to classes... Debugging in old way did work. Bcs. this bug JIRA has title "HCR doesnt work on OpenShift" and is resolved as done.
> Hot class reload doesn't work on OpenShift
> ------------------------------------------
>
> Key: JBIDE-21857
> URL: https://issues.jboss.org/browse/JBIDE-21857
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: openshift
> Affects Versions: 4.3.1.Beta2
> Reporter: Fred Bricon
> Assignee: Rob Stryker
> Fix For: 4.4.2.Final, 4.4.3.AM1, 4.5.0.AM1
>
> Attachments: HCRFailure.zip
>
>
> When enabling debug mode on an EAP server deployed on OpenShift, locally changing a class file will :
> - work sometimes when only the content of the method changed, but could fail in some other occasions with the Debugger saying the JDK is out of sync
> - will always fail if a method signature changed, the debugger saying JDK is out of sync
> Restarting the deployed module (with the .dodeploy flag) doesn't fixes the issue (as opposed to the same tweak ahen running on a local EAP server)
> This may be caused by running OpenJDK? Does it support the same level of debugging as Oracle JDK?
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
9 years, 4 months
[JBoss JIRA] (JBDS-4206) Convert existing ci jobs into matrix jobs
by Jan Richter (JIRA)
Jan Richter created JBDS-4206:
---------------------------------
Summary: Convert existing ci jobs into matrix jobs
Key: JBDS-4206
URL: https://issues.jboss.org/browse/JBDS-4206
Project: Red Hat JBoss Developer Studio (devstudio)
Issue Type: Task
Components: platform-installer
Affects Versions: 10.2.0.AM3
Reporter: Jan Richter
Priority: Critical
Instead of having a set of jobs for each platform, we should use matrix jobs to simplify the pipeline. Should also make tasks like JBDS-4185 much easier.
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
9 years, 4 months