[JBoss JIRA] (ERT-468) AssertionFailedException below ImageBuildDialog.createDialogArea (thrown in StructuredViewer.assertElementsNotNull) [EBZ#508026]
by Friendly Jira Robot (JIRA)
Friendly Jira Robot created ERT-468:
---------------------------------------
Summary: AssertionFailedException below ImageBuildDialog.createDialogArea (thrown in StructuredViewer.assertElementsNotNull) [EBZ#508026]
Key: ERT-468
URL: https://issues.jboss.org/browse/ERT-468
Project: Eclipse Release Train
Issue Type: Task
Components: Linux Tools
Reporter: Friendly Jira Robot
Fix For: Neon.2 (4.6)
The following problem was reported via the automated error reporting:
Message: Unhandled event loop exception
org.eclipse.core.runtime.AssertionFailedException: null argument:
at org.eclipse.jface.viewers.StructuredViewer.assertElementsNotNull(StructuredViewer.java:586)
at org.eclipse.jface.viewers.StructuredViewer.getRawChildren(StructuredViewer.java:1002)
at org.eclipse.jface.viewers.StructuredViewer.getFilteredChildren(StructuredViewer.java:907)
at org.eclipse.jface.viewers.StructuredViewer.getSortedChildren(StructuredViewer.java:1084)
at org.eclipse.jface.viewers.AbstractListViewer.inputChanged(AbstractListViewer.java:318)
at org.eclipse.jface.viewers.ContentViewer.setInput(ContentViewer.java:286)
at org.eclipse.jface.viewers.StructuredViewer.setInput(StructuredViewer.java:1696)
at org.eclipse.linuxtools.internal.docker.ui.wizards.ImageBuildDialog.createDialogArea(ImageBuildDialog.java:118)
at org.eclipse.jface.dialogs.Dialog.createContents(Dialog.java:767)
at org.eclipse.jface.window.Window.create(Window.java:426)
at org.eclipse.jface.dialogs.Dialog.create(Dialog.java:1095)
at org.eclipse.jface.window.Window.open(Window.java:783)
at org.eclipse.linuxtools.internal.docker.ui.launch.BuildDockerImageShortcut.createConfiguration(BuildDockerImageShortcut.java:109)
at org.eclipse.linuxtools.internal.docker.ui.launch.BaseResourceAwareLaunchShortcut.findLaunchConfiguration(BaseResourceAwareLaunchShortcut.java:84)
at org.eclipse.linuxtools.internal.docker.ui.launch.BuildDockerImageShortcut.launch(BuildDockerImageShortcut.java:61)
at org.eclipse.linuxtools.internal.docker.ui.launch.BaseResourceAwareLaunchShortcut.launch(BaseResourceAwareLaunchShortcut.java:41)
at org.eclipse.debug.internal.ui.launchConfigurations.LaunchShortcutExtension.launch(LaunchShortcutExtension.java:431)
at org.eclipse.debug.internal.ui.actions.LaunchShortcutAction.run(LaunchShortcutAction.java:74)
at org.eclipse.debug.internal.ui.actions.LaunchShortcutAction.runWithEvent(LaunchShortcutAction.java:123)
at org.eclipse.jface.action.ActionContributionItem.handleWidgetSelection(ActionContributionItem.java:565)
at org.eclipse.jface.action.ActionContributionItem.lambda$4(ActionContributionItem.java:397)
at org.eclipse.swt.widgets.EventTable.sendEvent(EventTable.java:84)
Bundles:
| org.eclipse.debug.ui | 3.11.200.v20160518-1858 | 3.11.200.v20160518-1858 |
| org.eclipse.jface | 3.12.0.v20160518-1929 | 3.12.0.v20160518-1929 |
| org.eclipse.linuxtools.docker.ui | 2.1.0.201609141916 | 2.1.0.201609141916 |
| org.eclipse.swt | 3.105.0.v20160603-0902 | 3.105.0.v20160603-0902 |
Operating Systems:
| Windows | 10.0.0 | 10.0.0 |
The above information is a snapshot of the collected data. Visit https://dev.eclipse.org/recommenders/committers/aeri/v2/#!/problems/580dd... 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-467) DockerException in ProcessLauncher$FluentProcessBuilder.<init> [EBZ#507163]
by Friendly Jira Robot (JIRA)
[ https://issues.jboss.org/browse/ERT-467?page=com.atlassian.jira.plugin.sy... ]
Friendly Jira Robot resolved ERT-467.
-------------------------------------
Resolution: Done
> DockerException in ProcessLauncher$FluentProcessBuilder.<init> [EBZ#507163]
> ---------------------------------------------------------------------------
>
> Key: ERT-467
> URL: https://issues.jboss.org/browse/ERT-467
> Project: Eclipse Release Train
> Issue Type: Task
> Components: Linux Tools
> Reporter: Friendly Jira Robot
> Labels: 5.2.0, Docker, bzira
> Fix For: Neon.2 (4.6)
>
>
> The following problem was reported via the automated error reporting:
> Message: The 'docker-compose.exe' command could not be located in 'C:\Program Files\Docker Toolbox'
> org.eclipse.linuxtools.docker.core.DockerException: The 'docker-compose.exe' command could not be located in 'C:\Program Files\Docker Toolbox'
> at org.eclipse.linuxtools.internal.docker.core.ProcessLauncher$FluentProcessBuilder.<init>(ProcessLauncher.java:87)
> at org.eclipse.linuxtools.internal.docker.core.ProcessLauncher$FluentProcessBuilder.<init>(ProcessLauncher.java:79)
> at org.eclipse.linuxtools.internal.docker.core.ProcessLauncher.processBuilder(ProcessLauncher.java:60)
> at org.eclipse.linuxtools.internal.docker.core.DockerCompose.up(DockerCompose.java:81)
> at org.eclipse.linuxtools.internal.docker.ui.jobs.DockerComposeUpJob.lambda$0(DockerComposeUpJob.java:88)
> at java.lang.Thread.run(null:-1)
> Bundles:
> | org.eclipse.linuxtools.docker.core | 2.1.0.201609141916 | 2.1.0.201609141916 |
> | org.eclipse.linuxtools.docker.ui | 2.1.0.201609141916 | 2.1.0.201609141916 |
> Operating Systems:
> | Windows | 10.0.0 | 10.0.0 |
> The above information is a snapshot of the collected data. Visit https://dev.eclipse.org/recommenders/committers/aeri/v2/#!/problems/5814a... 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-467) DockerException in ProcessLauncher$FluentProcessBuilder.<init> [EBZ#507163]
by Friendly Jira Robot (JIRA)
Friendly Jira Robot created ERT-467:
---------------------------------------
Summary: DockerException in ProcessLauncher$FluentProcessBuilder.<init> [EBZ#507163]
Key: ERT-467
URL: https://issues.jboss.org/browse/ERT-467
Project: Eclipse Release Train
Issue Type: Task
Components: Linux Tools
Reporter: Friendly Jira Robot
Fix For: Neon.2 (4.6)
The following problem was reported via the automated error reporting:
Message: The 'docker-compose.exe' command could not be located in 'C:\Program Files\Docker Toolbox'
org.eclipse.linuxtools.docker.core.DockerException: The 'docker-compose.exe' command could not be located in 'C:\Program Files\Docker Toolbox'
at org.eclipse.linuxtools.internal.docker.core.ProcessLauncher$FluentProcessBuilder.<init>(ProcessLauncher.java:87)
at org.eclipse.linuxtools.internal.docker.core.ProcessLauncher$FluentProcessBuilder.<init>(ProcessLauncher.java:79)
at org.eclipse.linuxtools.internal.docker.core.ProcessLauncher.processBuilder(ProcessLauncher.java:60)
at org.eclipse.linuxtools.internal.docker.core.DockerCompose.up(DockerCompose.java:81)
at org.eclipse.linuxtools.internal.docker.ui.jobs.DockerComposeUpJob.lambda$0(DockerComposeUpJob.java:88)
at java.lang.Thread.run(null:-1)
Bundles:
| org.eclipse.linuxtools.docker.core | 2.1.0.201609141916 | 2.1.0.201609141916 |
| org.eclipse.linuxtools.docker.ui | 2.1.0.201609141916 | 2.1.0.201609141916 |
Operating Systems:
| Windows | 10.0.0 | 10.0.0 |
The above information is a snapshot of the collected data. Visit https://dev.eclipse.org/recommenders/committers/aeri/v2/#!/problems/5814a... 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] (JBIDE-22376) Enable JMX when entering Debug mode
by Andre Dietisheim (JIRA)
[ https://issues.jboss.org/browse/JBIDE-22376?page=com.atlassian.jira.plugi... ]
Andre Dietisheim edited comment on JBIDE-22376 at 11/29/16 6:40 PM:
--------------------------------------------------------------------
[~mlabuda] as stated [here|https://issues.jboss.org/browse/JBIDE-21857?focusedCommentId=1333105...] jmx being connected isnt required for me to reproduce the simple case. What doesnt work for you when HCR'ing if the JMX node in the Servers view isnt connected (it states "[Disconnected]" without user connecting it manually)? I suspect the node not to reflect whether jmx is being used or not when hot-code-replacing/debugging. I suspect it to reflect if the MBeans are loaded.
[~rob.stryker] can you please chime in and provide the details?
was (Author: adietish):
[~mlabuda] as stated [here|https://issues.jboss.org/browse/JBIDE-21857?focusedCommentId=1333105...] jmx being connected isnt required for me to reproduce the simple case. What doesnt work for you when HCR'ing if the JMX node in the Servers view isnt connected (it states "[Disconnected]" without user connecting it manually)?
> Enable JMX when entering Debug mode
> -----------------------------------
>
> Key: JBIDE-22376
> URL: https://issues.jboss.org/browse/JBIDE-22376
> Project: Tools (JBoss Tools)
> Issue Type: Enhancement
> Components: jmx, openshift
> Affects Versions: 4.1.1.Beta1
> Reporter: Thomas Mäder
> Assignee: Rob Stryker
> Fix For: 4.4.2.Final, 4.4.3.AM1, 4.5.0.AM1
>
>
> We need to update the deployment configuration when entering debug mode. It is not entirely clear how to determine that an Openshift Pod has indeed a wildfly/EAP in it and can be reached with remoting-jmx
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
9 years, 4 months
[JBoss JIRA] (JBIDE-23320) New server window server type picker is single line long on Cinnamon
by Rob Stryker (JIRA)
[ https://issues.jboss.org/browse/JBIDE-23320?page=com.atlassian.jira.plugi... ]
Rob Stryker resolved JBIDE-23320.
---------------------------------
Resolution: Done
This is fixed upstream master and in upstream servertools 3.8.2.
I'm not sure if that's in our new TP yet or not, so we may need to adjust the fix versions. However, if [~mjurc] can test with just an upstream eclipse and none of JBT installed to verify, that'd be great.
> New server window server type picker is single line long on Cinnamon
> --------------------------------------------------------------------
>
> Key: JBIDE-23320
> URL: https://issues.jboss.org/browse/JBIDE-23320
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: server, upstream
> Environment: Fedora 24 x86-64
> Cinnamon 3.0.7
> Linux 4.7.6
> JBDS 10.1.0.GA
> Reporter: Michal Jurc
> Assignee: Rob Stryker
> Fix For: 4.4.3.AM1, 4.5.0.AM1
>
> Attachments: jbds-10.1-new-server.png
>
>
> In JBoss Developer Studio 10.1.0.GA, the New Server window server type choice only displays single server at time without scrolling which is uncomfortable to navigate through.
> Screenshot attached.
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
9 years, 4 months
[JBoss JIRA] (JBIDE-23294) Console is badly rendering some characters when starting Container Development Environment
by Rob Stryker (JIRA)
[ https://issues.jboss.org/browse/JBIDE-23294?page=com.atlassian.jira.plugi... ]
Rob Stryker updated JBIDE-23294:
--------------------------------
Fix Version/s: LATER
> Console is badly rendering some characters when starting Container Development Environment
> ------------------------------------------------------------------------------------------
>
> Key: JBIDE-23294
> URL: https://issues.jboss.org/browse/JBIDE-23294
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: cdk, server
> Affects Versions: 4.4.1.Final
> Reporter: Aurélien Pupier
> Assignee: Rob Stryker
> Priority: Minor
> Fix For: LATER
>
> Attachments: screenshot-1.png
>
>
> - there is a special character before the [KProgress
> - what means K for KProgress?
> {noformat}
> Bringing machine 'default' up with 'virtualbox' provider...
> ==> default: Importing base box 'cdkv2'...
> [KProgress: 10%
> [KProgress: 20%
> [KProgress: 90%
> [K==> default: Matching MAC address for NAT networking...
> {noformat}
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
9 years, 4 months