[JBoss JIRA] (JBIDE-23016) When starting CDK 2.2 with landrush for the first time, user will be prompted for sudo password
by Martin Malina (JIRA)
[ https://issues.jboss.org/browse/JBIDE-23016?page=com.atlassian.jira.plugi... ]
Martin Malina updated JBIDE-23016:
----------------------------------
Fix Version/s: 4.4.1.Final
> When starting CDK 2.2 with landrush for the first time, user will be prompted for sudo password
> -----------------------------------------------------------------------------------------------
>
> Key: JBIDE-23016
> URL: https://issues.jboss.org/browse/JBIDE-23016
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: cdk
> Affects Versions: 4.4.1.AM3
> Reporter: Martin Malina
> Assignee: Rob Stryker
> Fix For: 4.4.1.Final
>
>
> The problem is that the first time you do vagrant up with cdk that has landrush set up, you will be asked to provide your sudo password so that landrush can be set up (unless you used it elsewhere already).
> This is definitely true on Mac, most likely on Linux also. On Windows, I expect that you will probably just be shown the system prompt for agreeing that the process uses admin rights.
> When I did this yesterday (while testing cdk 2.2 rc1), I actually started it from terminal first, so I could enter my password in the console. But I'm pretty sure this wouldn't work in Eclipse. So we need to figure out how to handle this scenario and also test what happens on Windows after installing devsuite and then starting cdk from devstudio - that is our most important use case.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 7 months
[JBoss JIRA] (JBIDE-23010) landrush plugin prevents CDK server adapter from starting
by Martin Malina (JIRA)
[ https://issues.jboss.org/browse/JBIDE-23010?page=com.atlassian.jira.plugi... ]
Martin Malina commented on JBIDE-23010:
---------------------------------------
{quote}
And then I first started this from CLI - it wanted password for sudo to set up landrush. (That's another concern I have: How will this work in devstudio? Probably it won't.)
{quote}
I created a new issue for this: JBIDE-23016
> landrush plugin prevents CDK server adapter from starting
> ---------------------------------------------------------
>
> Key: JBIDE-23010
> URL: https://issues.jboss.org/browse/JBIDE-23010
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: cdk, upstream
> Affects Versions: 4.4.1.AM3
> Reporter: Martin Malina
> Assignee: Rob Stryker
> Priority: Critical
>
> Today I downloaded cdk 2.2.rc1 [1], installed all the vagrant plugins from scratch. And then I first started this from CLI - it wanted password for sudo to set up landrush. (That's another concern I have: How will this work in devstudio? Probably it won't.)
> Then I stopped it, set up in devstudio and start there. Everything looks fine, but the server adapter is stuck at "Starting...".
> This is the console output:
> {code}
> Bringing machine 'default' up with 'virtualbox' provider...
> ==> default: Clearing any previously set forwarded ports...
> ==> default: Clearing any previously set network interfaces...
> ==> default: [landrush] virtualbox requires an additional private network; adding it
> ==> default: [landrush] starting dns server
> ==> default: Preparing network interfaces based on configuration...
> default: Adapter 1: nat
> default: Adapter 2: hostonly
> ==> default: Forwarding ports...
> default: 22 (guest) => 2222 (host) (adapter 1)
> ==> default: Running 'pre-boot' VM customizations...
> ==> default: Booting VM...
> ==> default: Waiting for machine to boot. This may take a few minutes...
> default: SSH address: 127.0.0.1:2222
> default: SSH username: vagrant
> default: SSH auth method: private key
> default: Warning: Remote connection disconnect. Retrying...
> default: Warning: Remote connection disconnect. Retrying...
> default: Warning: Remote connection disconnect. Retrying...
> ==> default: Machine booted and ready!
> ==> default: Registering box with vagrant-registration...
> ==> default: Checking for guest additions in VM...
> default: No guest additions were detected on the base box for this VM! Guest
> default: additions are required for forwarded ports, shared folders, host only
> default: networking, and more. If SSH fails on this machine, please install
> default: the guest additions and repackage the box to continue.
> default:
> default: This is not an error message; everything may continue to work properly,
> default: in which case you may ignore this message.
> ==> default: Setting hostname...
> ==> default: Configuring and enabling network interfaces...
> [landrush] Using eth1 (172.28.128.3)
> ==> default: [landrush] adding machine entry: cdk.vm => 172.28.128.3
> ==> default: [landrush] adding static DNS entry: cdk => cdk.vm
> [landrush] Using eth1 (172.28.128.3)
> [landrush] Host DNS resolver config looks good.
> ==> default: Copying TLS certificates to /Users/rasp/jbossqa/cdk2.2.rc1/cdk/components/rhel/rhel-ose/.vagrant/machines/default/virtualbox/docker
> ==> default: Mounting SSHFS shared folder...
> ==> default: Mounting folder via SSHFS: /Users/rasp => /Users/rasp
> ==> default: Checking Mount..
> ==> default: Checking Mount..
> ==> default: Folder Successfully Mounted!
> ==> default: Machine already provisioned. Run `vagrant provision` or use the `--provision`
> ==> default: flag to force provisioning. Provisioners marked to run always will still run.
> ==> default: Running provisioner: shell...
> default: Running: inline script
> ==> default: Running provisioner: shell...
> default: Running: inline script
> ==> default:
> ==> default: Successfully started and provisioned VM with 2 cores and 3072 MB of memory.
> ==> default: To modify the number of cores and/or available memory set the environment variables
> ==> default: VM_CPU respectively VM_MEMORY.
> ==> default:
> ==> default: You can now access the OpenShift console on: https://openshift.cdk:8443/console
> ==> default:
> ==> default: To use OpenShift CLI, run:
> ==> default: $ vagrant ssh
> ==> default: $ oc login
> ==> default:
> ==> default: Configured users are (<username>/<password>):
> ==> default: openshift-dev/devel
> ==> default: admin/admin
> ==> default:
> ==> default: If you have the oc client library on your host, you can also login from your host.
> {code}
> These are my plugins:
> {code}
> $ vagrant plugin list
> landrush (1.1.1)
> - Version Constraint: 1.1.1
> vagrant-registration (1.2.3)
> - Version Constraint: 1.2.3
> vagrant-service-manager (1.3.0)
> - Version Constraint: 1.3.0
> vagrant-share (1.1.5, system)
> vagrant-sshfs (1.2.0)
> - Version Constraint: 1.2.0
> {code}
> [1] http://cdk-builds.usersys.redhat.com/builds/weekly/12-Aug-2016.rc1/
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 7 months
[JBoss JIRA] (JBIDE-23001) Application Wizard: NPE when opening OS 2 wizard from central or shell menu
by Andre Dietisheim (JIRA)
[ https://issues.jboss.org/browse/JBIDE-23001?page=com.atlassian.jira.plugi... ]
Andre Dietisheim commented on JBIDE-23001:
------------------------------------------
tested the PR, works for me.
We should make sure that we have an integration test for this.
> Application Wizard: NPE when opening OS 2 wizard from central or shell menu
> ---------------------------------------------------------------------------
>
> Key: JBIDE-23001
> URL: https://issues.jboss.org/browse/JBIDE-23001
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: openshift
> Affects Versions: 4.4.1.AM3
> Reporter: Marián Labuda
> Assignee: Dmitrii Bocharov
> Priority: Critical
> Labels: application_wizard, openshift_v2, regression
> Fix For: 4.4.1.Final
>
>
> When I am opening a New OpenShift Application wizard for OpenShift 2 connections, I get an NPE. This is caused only when opening wizard from shell menu File - New - OpenShift Application or from Central.
> stack trace of NPE:
> {code}
> Problems occurred when invoking code from plug-in: "org.eclipse.jface".
> java.lang.NullPointerException
> at org.jboss.tools.openshift.internal.common.ui.connection.ConnectionWizardPage.onPageWillGetDeactivated(ConnectionWizardPage.java:408)
> at org.jboss.tools.openshift.internal.common.ui.wizard.AbstractOpenShiftWizardPage$3.handlePageChanging(AbstractOpenShiftWizardPage.java:121)
> at org.eclipse.jface.wizard.WizardDialog$7.run(WizardDialog.java:1540)
> 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.wizard.WizardDialog.firePageChanging(WizardDialog.java:1537)
> at org.eclipse.jface.wizard.WizardDialog.doPageChanging(WizardDialog.java:890)
> at org.eclipse.jface.wizard.WizardDialog.showPage(WizardDialog.java:1177)
> at org.eclipse.jface.wizard.WizardDialog.nextPressed(WizardDialog.java:876)
> at org.eclipse.jface.wizard.WizardDialog.buttonPressed(WizardDialog.java:419)
> at org.eclipse.jface.dialogs.Dialog$2.widgetSelected(Dialog.java:618)
> at org.eclipse.swt.widgets.TypedListener.handleEvent(TypedListener.java:249)
> at org.eclipse.swt.widgets.EventTable.sendEvent(EventTable.java:84)
> at org.eclipse.swt.widgets.Display.sendEvent(Display.java:5219)
> at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1340)
> at org.eclipse.swt.widgets.Display.runDeferredEvents(Display.java:4553)
> at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:4143)
> at org.eclipse.jface.window.Window.runEventLoop(Window.java:818)
> at org.eclipse.jface.window.Window.open(Window.java:794)
> at org.jboss.tools.central.internal.WizardSupport.openWizard(WizardSupport.java:71)
> at org.jboss.tools.central.editors.GettingStartedHtmlPage$9.run(GettingStartedHtmlPage.java:431)
> 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:4528)
> at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:4146)
> 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:498)
> 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)
> {code}
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 7 months
[JBoss JIRA] (JBIDE-23016) When starting CDK 2.2 with landrush for the first time, user will be prompted for sudo password
by Martin Malina (JIRA)
[ https://issues.jboss.org/browse/JBIDE-23016?page=com.atlassian.jira.plugi... ]
Martin Malina reassigned JBIDE-23016:
-------------------------------------
Assignee: Rob Stryker
> When starting CDK 2.2 with landrush for the first time, user will be prompted for sudo password
> -----------------------------------------------------------------------------------------------
>
> Key: JBIDE-23016
> URL: https://issues.jboss.org/browse/JBIDE-23016
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: cdk
> Affects Versions: 4.4.1.AM3
> Reporter: Martin Malina
> Assignee: Rob Stryker
>
> The problem is that the first time you do vagrant up with cdk that has landrush set up, you will be asked to provide your sudo password so that landrush can be set up (unless you used it elsewhere already).
> This is definitely true on Mac, most likely on Linux also. On Windows, I expect that you will probably just be shown the system prompt for agreeing that the process uses admin rights.
> When I did this yesterday (while testing cdk 2.2 rc1), I actually started it from terminal first, so I could enter my password in the console. But I'm pretty sure this wouldn't work in Eclipse. So we need to figure out how to handle this scenario and also test what happens on Windows after installing devsuite and then starting cdk from devstudio - that is our most important use case.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 7 months
[JBoss JIRA] (JBIDE-23016) When starting CDK 2.2 with landrush for the first time, user will be prompted for sudo password
by Martin Malina (JIRA)
Martin Malina created JBIDE-23016:
-------------------------------------
Summary: When starting CDK 2.2 with landrush for the first time, user will be prompted for sudo password
Key: JBIDE-23016
URL: https://issues.jboss.org/browse/JBIDE-23016
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: cdk
Affects Versions: 4.4.1.AM3
Reporter: Martin Malina
The problem is that the first time you do vagrant up with cdk that has landrush set up, you will be asked to provide your sudo password so that landrush can be set up (unless you used it elsewhere already).
This is definitely true on Mac, most likely on Linux also. On Windows, I expect that you will probably just be shown the system prompt for agreeing that the process uses admin rights.
When I did this yesterday (while testing cdk 2.2 rc1), I actually started it from terminal first, so I could enter my password in the console. But I'm pretty sure this wouldn't work in Eclipse. So we need to figure out how to handle this scenario and also test what happens on Windows after installing devsuite and then starting cdk from devstudio - that is our most important use case.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 7 months
[JBoss JIRA] (JBIDE-23011) Docker Explorer broken on Windows
by Martin Malina (JIRA)
[ https://issues.jboss.org/browse/JBIDE-23011?page=com.atlassian.jira.plugi... ]
Martin Malina edited comment on JBIDE-23011 at 8/17/16 5:22 AM:
----------------------------------------------------------------
[~nickboldt]:
{quote}
As of EOD on 2016-08-16, the fix for this will be in the Docker Tools nightly site.
{quote}
There was actually a problem with the fix - java.lang.IndexOutOfBoundsException - so a new fix is coming now and will be available shortly.
{quote}
So, users of JBT 4.4.1.AM3 or devstudio 10.1.0.AM3 can get the fix via:
Help > Install new software > Work with: http://download.eclipse.org/linuxtools/updates-docker-nightly/ > select Docker Tooling > install. Restart when prompted.
{quote}
You can't really do this in devstudio because docker tooling is part of the product definition, no? So you can update from another source. At least that's my understanding. But we don't release devstudio for AM3, only JBoss Tools, right? So we should be good.
Update: Xavier tells me that this should really work even with devstudio - "we verified that there is no version lock-down on this component in DevStudio". But the fact about not releasing devstudio at this time stands correct AFAIK.
was (Author: mmalina):
[~nickboldt]:
{quote}
As of EOD on 2016-08-16, the fix for this will be in the Docker Tools nightly site.
{quote}
There was actually a problem with the fix - java.lang.IndexOutOfBoundsException - so a new fix is coming now and will be available shortly.
{quote}
So, users of JBT 4.4.1.AM3 or devstudio 10.1.0.AM3 can get the fix via:
Help > Install new software > Work with: http://download.eclipse.org/linuxtools/updates-docker-nightly/ > select Docker Tooling > install. Restart when prompted.
{quote}
You can't really do this in devstudio because docker tooling is part of the product definition, no? So you can update from another source. At least that's my understanding. But we don't release devstudio for AM3, only JBoss Tools, right? So we should be good.
> Docker Explorer broken on Windows
> ---------------------------------
>
> Key: JBIDE-23011
> URL: https://issues.jboss.org/browse/JBIDE-23011
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: docker
> Affects Versions: 4.4.1.AM3
> Reporter: Martin Malina
> Assignee: Xavier Coulon
> Priority: Critical
> Fix For: 4.4.1.Final
>
> Attachments: docker-explorer.jpg, jbide23011.png, jbide23011_2.png
>
>
> [reply] [−] Description Martin Malina CLA Friend 2016-08-16 08:51:31 EDT
> Created attachment 263612 [details]
> Broken Docker Explorer view
> I just installed a brand new installation of Red Hat JBoss Developer Studio 10.1.0.AM3 which contains Docker Tooling 2.1.0.201608101805 on Windows and when I open Docker Explorer, it contains a red X and "Failed to create the part's controls". Also, there is a button that says Details > >.
> There is this NPE in the error log view:
> {code}
> java.lang.NullPointerException
> at org.eclipse.linuxtools.docker.core.DockerConnectionManager.reloadConnections(DockerConnectionManager.java:63)
> at org.eclipse.linuxtools.docker.core.DockerConnectionManager.<init>(DockerConnectionManager.java:50)
> at org.eclipse.linuxtools.docker.core.DockerConnectionManager.getInstance(DockerConnectionManager.java:44)
> at org.eclipse.linuxtools.internal.docker.ui.views.DockerExplorerView.getInitialInput(DockerExplorerView.java:93)
> at org.eclipse.ui.navigator.CommonNavigator.createPartControl(CommonNavigator.java:206)
> at org.eclipse.linuxtools.internal.docker.ui.views.DockerExplorerView.createConnectionsPane(DockerExplorerView.java:195)
> at org.eclipse.linuxtools.internal.docker.ui.views.DockerExplorerView.createPartControl(DockerExplorerView.java:147)
> at org.eclipse.ui.internal.e4.compatibility.CompatibilityPart.createPartControl(CompatibilityPart.java:151)
> at org.eclipse.ui.internal.e4.compatibility.CompatibilityView.createPartControl(CompatibilityView.java:143)
> at org.eclipse.ui.internal.e4.compatibility.CompatibilityPart.create(CompatibilityPart.java:341)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at sun.reflect.NativeMethodAccessorImpl.invoke(Unknown Source)
> at sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source)
> at java.lang.reflect.Method.invoke(Unknown Source)
> at org.eclipse.e4.core.internal.di.MethodRequestor.execute(MethodRequestor.java:54)
> at org.eclipse.e4.core.internal.di.InjectorImpl.processAnnotated(InjectorImpl.java:966)
> at org.eclipse.e4.core.internal.di.InjectorImpl.processAnnotated(InjectorImpl.java:931)
> at org.eclipse.e4.core.internal.di.InjectorImpl.inject(InjectorImpl.java:151)
> at org.eclipse.e4.core.internal.di.InjectorImpl.internalMake(InjectorImpl.java:375)
> at org.eclipse.e4.core.internal.di.InjectorImpl.make(InjectorImpl.java:294)
> at org.eclipse.e4.core.contexts.ContextInjectionFactory.make(ContextInjectionFactory.java:162)
> at org.eclipse.e4.ui.internal.workbench.ReflectionContributionFactory.createFromBundle(ReflectionContributionFactory.java:105)
> at org.eclipse.e4.ui.internal.workbench.ReflectionContributionFactory.doCreate(ReflectionContributionFactory.java:74)
> at org.eclipse.e4.ui.internal.workbench.ReflectionContributionFactory.create(ReflectionContributionFactory.java:56)
> at org.eclipse.e4.ui.workbench.renderers.swt.ContributedPartRenderer.createWidget(ContributedPartRenderer.java:129)
> at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine.createWidget(PartRenderingEngine.java:975)
> at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine.safeCreateGui(PartRenderingEngine.java:651)
> at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine$1.run(PartRenderingEngine.java:536)
> at org.eclipse.core.runtime.SafeRunner.run(SafeRunner.java:42)
> at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine.createGui(PartRenderingEngine.java:520)
> at org.eclipse.e4.ui.workbench.renderers.swt.ElementReferenceRenderer.createWidget(ElementReferenceRenderer.java:70)
> at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine.createWidget(PartRenderingEngine.java:975)
> at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine.safeCreateGui(PartRenderingEngine.java:651)
> at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine.safeCreateGui(PartRenderingEngine.java:757)
> at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine.access$0(PartRenderingEngine.java:728)
> at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine$2.run(PartRenderingEngine.java:722)
> at org.eclipse.core.runtime.SafeRunner.run(SafeRunner.java:42)
> at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine.createGui(PartRenderingEngine.java:706)
> at org.eclipse.e4.ui.workbench.renderers.swt.StackRenderer.showTab(StackRenderer.java:1317)
> at org.eclipse.e4.ui.workbench.renderers.swt.LazyStackRenderer$1.handleEvent(LazyStackRenderer.java:72)
> at org.eclipse.e4.ui.services.internal.events.UIEventHandler$1.run(UIEventHandler.java:40)
> at org.eclipse.swt.widgets.Synchronizer.syncExec(Synchronizer.java:233)
> at org.eclipse.ui.internal.UISynchronizer.syncExec(UISynchronizer.java:145)
> at org.eclipse.swt.widgets.Display.syncExec(Display.java:4813)
> at org.eclipse.e4.ui.internal.workbench.swt.E4Application$1.syncExec(E4Application.java:211)
> at org.eclipse.e4.ui.services.internal.events.UIEventHandler.handleEvent(UIEventHandler.java:36)
> at org.eclipse.equinox.internal.event.EventHandlerWrapper.handleEvent(EventHandlerWrapper.java:201)
> at org.eclipse.equinox.internal.event.EventHandlerTracker.dispatchEvent(EventHandlerTracker.java:197)
> at org.eclipse.equinox.internal.event.EventHandlerTracker.dispatchEvent(EventHandlerTracker.java:1)
> at org.eclipse.osgi.framework.eventmgr.EventManager.dispatchEvent(EventManager.java:230)
> at org.eclipse.osgi.framework.eventmgr.ListenerQueue.dispatchEventSynchronous(ListenerQueue.java:148)
> at org.eclipse.equinox.internal.event.EventAdminImpl.dispatchEvent(EventAdminImpl.java:135)
> at org.eclipse.equinox.internal.event.EventAdminImpl.sendEvent(EventAdminImpl.java:78)
> at org.eclipse.equinox.internal.event.EventComponent.sendEvent(EventComponent.java:39)
> at org.eclipse.e4.ui.services.internal.events.EventBroker.send(EventBroker.java:94)
> at org.eclipse.e4.ui.internal.workbench.UIEventPublisher.notifyChanged(UIEventPublisher.java:60)
> at org.eclipse.emf.common.notify.impl.BasicNotifierImpl.eNotify(BasicNotifierImpl.java:374)
> at org.eclipse.e4.ui.model.application.ui.impl.ElementContainerImpl.setSelectedElement(ElementContainerImpl.java:173)
> at org.eclipse.e4.ui.internal.workbench.ModelServiceImpl.showElementInWindow(ModelServiceImpl.java:617)
> at org.eclipse.e4.ui.internal.workbench.ModelServiceImpl.bringToTop(ModelServiceImpl.java:581)
> at org.eclipse.e4.ui.internal.workbench.PartServiceImpl.delegateBringToTop(PartServiceImpl.java:770)
> at org.eclipse.e4.ui.internal.workbench.PartServiceImpl.activate(PartServiceImpl.java:744)
> at org.eclipse.e4.ui.internal.workbench.PartServiceImpl.activate(PartServiceImpl.java:682)
> at org.eclipse.e4.ui.internal.workbench.PartServiceImpl.activate(PartServiceImpl.java:677)
> at org.eclipse.e4.ui.internal.workbench.PartServiceImpl.showPart(PartServiceImpl.java:1205)
> at org.eclipse.ui.internal.WorkbenchPage.showPart(WorkbenchPage.java:1283)
> at org.eclipse.ui.internal.WorkbenchPage.busyShowView(WorkbenchPage.java:1274)
> at org.eclipse.ui.internal.WorkbenchPage$12.run(WorkbenchPage.java:4316)
> at org.eclipse.swt.custom.BusyIndicator.showWhile(BusyIndicator.java:70)
> at org.eclipse.ui.internal.WorkbenchPage.showView(WorkbenchPage.java:4312)
> at org.eclipse.ui.internal.WorkbenchPage.showView(WorkbenchPage.java:4292)
> at org.eclipse.ui.internal.quickaccess.ViewElement.execute(ViewElement.java:77)
> at org.eclipse.ui.internal.quickaccess.SearchField$2.handleElementSelected(SearchField.java:200)
> at org.eclipse.ui.internal.quickaccess.QuickAccessContents.handleSelection(QuickAccessContents.java:507)
> at org.eclipse.ui.internal.quickaccess.QuickAccessContents.access$0(QuickAccessContents.java:497)
> at org.eclipse.ui.internal.quickaccess.QuickAccessContents$1.keyPressed(QuickAccessContents.java:542)
> at org.eclipse.swt.widgets.TypedListener.handleEvent(TypedListener.java:168)
> at org.eclipse.swt.widgets.EventTable.sendEvent(EventTable.java:84)
> at org.eclipse.swt.widgets.Display.sendEvent(Display.java:4410)
> at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1079)
> at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1103)
> at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1088)
> at org.eclipse.swt.widgets.Widget.sendKeyEvent(Widget.java:1130)
> at org.eclipse.swt.widgets.Text.sendKeyEvent(Text.java:1789)
> at org.eclipse.swt.widgets.Widget.sendKeyEvent(Widget.java:1126)
> at org.eclipse.swt.widgets.Widget.wmChar(Widget.java:1547)
> at org.eclipse.swt.widgets.Control.WM_CHAR(Control.java:4910)
> at org.eclipse.swt.widgets.Text.WM_CHAR(Text.java:2722)
> at org.eclipse.swt.widgets.Control.windowProc(Control.java:4791)
> at org.eclipse.swt.widgets.Text.windowProc(Text.java:2704)
> at org.eclipse.swt.widgets.Display.windowProc(Display.java:5102)
> at org.eclipse.swt.internal.win32.OS.DispatchMessageW(Native Method)
> at org.eclipse.swt.internal.win32.OS.DispatchMessage(OS.java:2552)
> at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:3814)
> 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(Unknown Source)
> at sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source)
> at java.lang.reflect.Method.invoke(Unknown Source)
> 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)
> {code}
> This is a tracking issue for this upstream BZ: https://bugs.eclipse.org/bugs/show_bug.cgi?id=499745
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 7 months
[JBoss JIRA] (JBIDE-23011) Docker Explorer broken on Windows
by Martin Malina (JIRA)
[ https://issues.jboss.org/browse/JBIDE-23011?page=com.atlassian.jira.plugi... ]
Martin Malina commented on JBIDE-23011:
---------------------------------------
[~nickboldt]:
{quote}
As of EOD on 2016-08-16, the fix for this will be in the Docker Tools nightly site.
{quote}
There was actually a problem with the fix - java.lang.IndexOutOfBoundsException - so a new fix is coming now and will be available shortly.
{quote}
So, users of JBT 4.4.1.AM3 or devstudio 10.1.0.AM3 can get the fix via:
Help > Install new software > Work with: http://download.eclipse.org/linuxtools/updates-docker-nightly/ > select Docker Tooling > install. Restart when prompted.
{quote}
You can't really do this in devstudio because docker tooling is part of the product definition, no? So you can update from another source. At least that's my understanding. But we don't release devstudio for AM3, only JBoss Tools, right? So we should be good.
> Docker Explorer broken on Windows
> ---------------------------------
>
> Key: JBIDE-23011
> URL: https://issues.jboss.org/browse/JBIDE-23011
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: docker
> Affects Versions: 4.4.1.AM3
> Reporter: Martin Malina
> Assignee: Xavier Coulon
> Priority: Critical
> Fix For: 4.4.1.Final
>
> Attachments: docker-explorer.jpg, jbide23011.png, jbide23011_2.png
>
>
> [reply] [−] Description Martin Malina CLA Friend 2016-08-16 08:51:31 EDT
> Created attachment 263612 [details]
> Broken Docker Explorer view
> I just installed a brand new installation of Red Hat JBoss Developer Studio 10.1.0.AM3 which contains Docker Tooling 2.1.0.201608101805 on Windows and when I open Docker Explorer, it contains a red X and "Failed to create the part's controls". Also, there is a button that says Details > >.
> There is this NPE in the error log view:
> {code}
> java.lang.NullPointerException
> at org.eclipse.linuxtools.docker.core.DockerConnectionManager.reloadConnections(DockerConnectionManager.java:63)
> at org.eclipse.linuxtools.docker.core.DockerConnectionManager.<init>(DockerConnectionManager.java:50)
> at org.eclipse.linuxtools.docker.core.DockerConnectionManager.getInstance(DockerConnectionManager.java:44)
> at org.eclipse.linuxtools.internal.docker.ui.views.DockerExplorerView.getInitialInput(DockerExplorerView.java:93)
> at org.eclipse.ui.navigator.CommonNavigator.createPartControl(CommonNavigator.java:206)
> at org.eclipse.linuxtools.internal.docker.ui.views.DockerExplorerView.createConnectionsPane(DockerExplorerView.java:195)
> at org.eclipse.linuxtools.internal.docker.ui.views.DockerExplorerView.createPartControl(DockerExplorerView.java:147)
> at org.eclipse.ui.internal.e4.compatibility.CompatibilityPart.createPartControl(CompatibilityPart.java:151)
> at org.eclipse.ui.internal.e4.compatibility.CompatibilityView.createPartControl(CompatibilityView.java:143)
> at org.eclipse.ui.internal.e4.compatibility.CompatibilityPart.create(CompatibilityPart.java:341)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at sun.reflect.NativeMethodAccessorImpl.invoke(Unknown Source)
> at sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source)
> at java.lang.reflect.Method.invoke(Unknown Source)
> at org.eclipse.e4.core.internal.di.MethodRequestor.execute(MethodRequestor.java:54)
> at org.eclipse.e4.core.internal.di.InjectorImpl.processAnnotated(InjectorImpl.java:966)
> at org.eclipse.e4.core.internal.di.InjectorImpl.processAnnotated(InjectorImpl.java:931)
> at org.eclipse.e4.core.internal.di.InjectorImpl.inject(InjectorImpl.java:151)
> at org.eclipse.e4.core.internal.di.InjectorImpl.internalMake(InjectorImpl.java:375)
> at org.eclipse.e4.core.internal.di.InjectorImpl.make(InjectorImpl.java:294)
> at org.eclipse.e4.core.contexts.ContextInjectionFactory.make(ContextInjectionFactory.java:162)
> at org.eclipse.e4.ui.internal.workbench.ReflectionContributionFactory.createFromBundle(ReflectionContributionFactory.java:105)
> at org.eclipse.e4.ui.internal.workbench.ReflectionContributionFactory.doCreate(ReflectionContributionFactory.java:74)
> at org.eclipse.e4.ui.internal.workbench.ReflectionContributionFactory.create(ReflectionContributionFactory.java:56)
> at org.eclipse.e4.ui.workbench.renderers.swt.ContributedPartRenderer.createWidget(ContributedPartRenderer.java:129)
> at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine.createWidget(PartRenderingEngine.java:975)
> at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine.safeCreateGui(PartRenderingEngine.java:651)
> at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine$1.run(PartRenderingEngine.java:536)
> at org.eclipse.core.runtime.SafeRunner.run(SafeRunner.java:42)
> at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine.createGui(PartRenderingEngine.java:520)
> at org.eclipse.e4.ui.workbench.renderers.swt.ElementReferenceRenderer.createWidget(ElementReferenceRenderer.java:70)
> at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine.createWidget(PartRenderingEngine.java:975)
> at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine.safeCreateGui(PartRenderingEngine.java:651)
> at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine.safeCreateGui(PartRenderingEngine.java:757)
> at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine.access$0(PartRenderingEngine.java:728)
> at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine$2.run(PartRenderingEngine.java:722)
> at org.eclipse.core.runtime.SafeRunner.run(SafeRunner.java:42)
> at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine.createGui(PartRenderingEngine.java:706)
> at org.eclipse.e4.ui.workbench.renderers.swt.StackRenderer.showTab(StackRenderer.java:1317)
> at org.eclipse.e4.ui.workbench.renderers.swt.LazyStackRenderer$1.handleEvent(LazyStackRenderer.java:72)
> at org.eclipse.e4.ui.services.internal.events.UIEventHandler$1.run(UIEventHandler.java:40)
> at org.eclipse.swt.widgets.Synchronizer.syncExec(Synchronizer.java:233)
> at org.eclipse.ui.internal.UISynchronizer.syncExec(UISynchronizer.java:145)
> at org.eclipse.swt.widgets.Display.syncExec(Display.java:4813)
> at org.eclipse.e4.ui.internal.workbench.swt.E4Application$1.syncExec(E4Application.java:211)
> at org.eclipse.e4.ui.services.internal.events.UIEventHandler.handleEvent(UIEventHandler.java:36)
> at org.eclipse.equinox.internal.event.EventHandlerWrapper.handleEvent(EventHandlerWrapper.java:201)
> at org.eclipse.equinox.internal.event.EventHandlerTracker.dispatchEvent(EventHandlerTracker.java:197)
> at org.eclipse.equinox.internal.event.EventHandlerTracker.dispatchEvent(EventHandlerTracker.java:1)
> at org.eclipse.osgi.framework.eventmgr.EventManager.dispatchEvent(EventManager.java:230)
> at org.eclipse.osgi.framework.eventmgr.ListenerQueue.dispatchEventSynchronous(ListenerQueue.java:148)
> at org.eclipse.equinox.internal.event.EventAdminImpl.dispatchEvent(EventAdminImpl.java:135)
> at org.eclipse.equinox.internal.event.EventAdminImpl.sendEvent(EventAdminImpl.java:78)
> at org.eclipse.equinox.internal.event.EventComponent.sendEvent(EventComponent.java:39)
> at org.eclipse.e4.ui.services.internal.events.EventBroker.send(EventBroker.java:94)
> at org.eclipse.e4.ui.internal.workbench.UIEventPublisher.notifyChanged(UIEventPublisher.java:60)
> at org.eclipse.emf.common.notify.impl.BasicNotifierImpl.eNotify(BasicNotifierImpl.java:374)
> at org.eclipse.e4.ui.model.application.ui.impl.ElementContainerImpl.setSelectedElement(ElementContainerImpl.java:173)
> at org.eclipse.e4.ui.internal.workbench.ModelServiceImpl.showElementInWindow(ModelServiceImpl.java:617)
> at org.eclipse.e4.ui.internal.workbench.ModelServiceImpl.bringToTop(ModelServiceImpl.java:581)
> at org.eclipse.e4.ui.internal.workbench.PartServiceImpl.delegateBringToTop(PartServiceImpl.java:770)
> at org.eclipse.e4.ui.internal.workbench.PartServiceImpl.activate(PartServiceImpl.java:744)
> at org.eclipse.e4.ui.internal.workbench.PartServiceImpl.activate(PartServiceImpl.java:682)
> at org.eclipse.e4.ui.internal.workbench.PartServiceImpl.activate(PartServiceImpl.java:677)
> at org.eclipse.e4.ui.internal.workbench.PartServiceImpl.showPart(PartServiceImpl.java:1205)
> at org.eclipse.ui.internal.WorkbenchPage.showPart(WorkbenchPage.java:1283)
> at org.eclipse.ui.internal.WorkbenchPage.busyShowView(WorkbenchPage.java:1274)
> at org.eclipse.ui.internal.WorkbenchPage$12.run(WorkbenchPage.java:4316)
> at org.eclipse.swt.custom.BusyIndicator.showWhile(BusyIndicator.java:70)
> at org.eclipse.ui.internal.WorkbenchPage.showView(WorkbenchPage.java:4312)
> at org.eclipse.ui.internal.WorkbenchPage.showView(WorkbenchPage.java:4292)
> at org.eclipse.ui.internal.quickaccess.ViewElement.execute(ViewElement.java:77)
> at org.eclipse.ui.internal.quickaccess.SearchField$2.handleElementSelected(SearchField.java:200)
> at org.eclipse.ui.internal.quickaccess.QuickAccessContents.handleSelection(QuickAccessContents.java:507)
> at org.eclipse.ui.internal.quickaccess.QuickAccessContents.access$0(QuickAccessContents.java:497)
> at org.eclipse.ui.internal.quickaccess.QuickAccessContents$1.keyPressed(QuickAccessContents.java:542)
> at org.eclipse.swt.widgets.TypedListener.handleEvent(TypedListener.java:168)
> at org.eclipse.swt.widgets.EventTable.sendEvent(EventTable.java:84)
> at org.eclipse.swt.widgets.Display.sendEvent(Display.java:4410)
> at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1079)
> at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1103)
> at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1088)
> at org.eclipse.swt.widgets.Widget.sendKeyEvent(Widget.java:1130)
> at org.eclipse.swt.widgets.Text.sendKeyEvent(Text.java:1789)
> at org.eclipse.swt.widgets.Widget.sendKeyEvent(Widget.java:1126)
> at org.eclipse.swt.widgets.Widget.wmChar(Widget.java:1547)
> at org.eclipse.swt.widgets.Control.WM_CHAR(Control.java:4910)
> at org.eclipse.swt.widgets.Text.WM_CHAR(Text.java:2722)
> at org.eclipse.swt.widgets.Control.windowProc(Control.java:4791)
> at org.eclipse.swt.widgets.Text.windowProc(Text.java:2704)
> at org.eclipse.swt.widgets.Display.windowProc(Display.java:5102)
> at org.eclipse.swt.internal.win32.OS.DispatchMessageW(Native Method)
> at org.eclipse.swt.internal.win32.OS.DispatchMessage(OS.java:2552)
> at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:3814)
> 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(Unknown Source)
> at sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source)
> at java.lang.reflect.Method.invoke(Unknown Source)
> 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)
> {code}
> This is a tracking issue for this upstream BZ: https://bugs.eclipse.org/bugs/show_bug.cgi?id=499745
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 7 months