[JBoss JIRA] (ERT-216) Running image, which has shell form of CMD needs to be enclosed in quotes [EBZ#494555]
by Xavier Coulon (JIRA)
[ https://issues.jboss.org/browse/ERT-216?page=com.atlassian.jira.plugin.sy... ]
Xavier Coulon updated ERT-216:
------------------------------
Sprint: devex #115 May 2016
> Running image, which has shell form of CMD needs to be enclosed in quotes [EBZ#494555]
> --------------------------------------------------------------------------------------
>
> Key: ERT-216
> URL: https://issues.jboss.org/browse/ERT-216
> Project: Eclipse Release Train
> Issue Type: Task
> Components: Linux Tools
> Reporter: Friendly Jira Robot
> Assignee: Roland Grunberg
> Labels: Docker, bzira
>
> Running image, which was build using dockerfile with CMD in shell form (for example greyltc/lamp) needs to be enclosed in quotes.
> Steps to reproduce:
> * Pull image which was build using dockerfile with CMD in shell form (for example greyltc/lamp from docker hub)
> * In Docker Explorer right click that image -> Run
> * Assert: command should be the same as running that image from command line
> * FAIL: command is `/bin/sh -c start-servers; sleep infinity` instead of `/bin/sh -c 'start-servers; sleep infinity'`
> Those missing quotes causes that container to stop right after it was started (which is not desired)
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 10 months
[JBoss JIRA] (ERT-236) [compatibility] docker 1.10.x image IDs have digest prefix [EBZ#494770]
by Xavier Coulon (JIRA)
[ https://issues.jboss.org/browse/ERT-236?page=com.atlassian.jira.plugin.sy... ]
Xavier Coulon updated ERT-236:
------------------------------
Sprint: devex #115 May 2016
> [compatibility] docker 1.10.x image IDs have digest prefix [EBZ#494770]
> -----------------------------------------------------------------------
>
> Key: ERT-236
> URL: https://issues.jboss.org/browse/ERT-236
> Project: Eclipse Release Train
> Issue Type: Task
> Components: Linux Tools
> Reporter: Friendly Jira Robot
> Labels: 5.0.0, Docker, bzira
> Fix For: Neon (4.6)
>
>
> Docker 1.10.x (Remote API 1.22)
> Referring to images as "${digest}:${id}" seems to work just fine for the API, and probably expected given tha is what the full ID says. However from the POV of user presentation (Images/Containers view), we should strip out the digest part since the cli does the same.
> As an example :
> $ echo -e "GET /images/json?all=0 HTTP/1.1\r\n" | nc -U /var/run/docker.sock
> [
> ...
> ...
> {
> "Id": "sha256:77d2bd38e2e5fffae1d76af9b99a478c198218d9708c8bebf1932819a95db2bb",
> "ParentId": "",
> "RepoTags": [
> "docker.io/cassandra:3.5"
> ],
> "RepoDigests": null,
> "Created": 1462430641,
> "Size": 388722305,
> "VirtualSize": 388722305,
> "Labels": {
> }
> },
> {
> "Id": "sha256:88ecdbb5a908bd1bdbb921110a6134d6916f962680da0c4628102ff0691b38b3",
> "ParentId": "sha256:ec10611174d4a859aeb635cd1eef308e6d09cbb1b7f0936d46de62eafb39094a",
> "RepoTags": [
> "docker.io/registry:2"
> ],
> "RepoDigests": null,
> "Created": 1460576081,
> "Size": 171067126,
> "VirtualSize": 171067126,
> "Labels": {
> }
> }
> ...
> ...
> ]
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 10 months
[JBoss JIRA] (ERT-236) [compatibility] docker 1.10.x image IDs have digest prefix [EBZ#494770]
by Xavier Coulon (JIRA)
[ https://issues.jboss.org/browse/ERT-236?page=com.atlassian.jira.plugin.sy... ]
Xavier Coulon resolved ERT-236.
-------------------------------
Resolution: Done
Patch reviewed and merged
> [compatibility] docker 1.10.x image IDs have digest prefix [EBZ#494770]
> -----------------------------------------------------------------------
>
> Key: ERT-236
> URL: https://issues.jboss.org/browse/ERT-236
> Project: Eclipse Release Train
> Issue Type: Task
> Components: Linux Tools
> Reporter: Friendly Jira Robot
> Labels: 5.0.0, Docker, bzira
> Fix For: Neon (4.6)
>
>
> Docker 1.10.x (Remote API 1.22)
> Referring to images as "${digest}:${id}" seems to work just fine for the API, and probably expected given tha is what the full ID says. However from the POV of user presentation (Images/Containers view), we should strip out the digest part since the cli does the same.
> As an example :
> $ echo -e "GET /images/json?all=0 HTTP/1.1\r\n" | nc -U /var/run/docker.sock
> [
> ...
> ...
> {
> "Id": "sha256:77d2bd38e2e5fffae1d76af9b99a478c198218d9708c8bebf1932819a95db2bb",
> "ParentId": "",
> "RepoTags": [
> "docker.io/cassandra:3.5"
> ],
> "RepoDigests": null,
> "Created": 1462430641,
> "Size": 388722305,
> "VirtualSize": 388722305,
> "Labels": {
> }
> },
> {
> "Id": "sha256:88ecdbb5a908bd1bdbb921110a6134d6916f962680da0c4628102ff0691b38b3",
> "ParentId": "sha256:ec10611174d4a859aeb635cd1eef308e6d09cbb1b7f0936d46de62eafb39094a",
> "RepoTags": [
> "docker.io/registry:2"
> ],
> "RepoDigests": null,
> "Created": 1460576081,
> "Size": 171067126,
> "VirtualSize": 171067126,
> "Labels": {
> }
> }
> ...
> ...
> ]
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 10 months
[JBoss JIRA] (ERT-224) DockerException in DockerConnection.listContainers [EBZ#494871]
by Xavier Coulon (JIRA)
[ https://issues.jboss.org/browse/ERT-224?page=com.atlassian.jira.plugin.sy... ]
Xavier Coulon updated ERT-224:
------------------------------
Sprint: devex #115 May 2016
> DockerException in DockerConnection.listContainers [EBZ#494871]
> ---------------------------------------------------------------
>
> Key: ERT-224
> URL: https://issues.jboss.org/browse/ERT-224
> Project: Eclipse Release Train
> Issue Type: Task
> Components: Linux Tools
> Reporter: Friendly Jira Robot
> Labels: Docker, bzira
>
> The following problem was reported via the automated error reporting:
> Message: Timeout: GET https://192.168.99.101:2376/containers/json?all=1
> org.eclipse.linuxtools.docker.core.DockerException: Timeout: GET https://192.168.99.101:2376/containers/json?all=1
> at org.eclipse.linuxtools.internal.docker.core.DockerConnection.listContainers(DockerConnection.java:635)
> at org.eclipse.linuxtools.internal.docker.core.DockerConnection.getContainers(DockerConnection.java:483)
> at org.eclipse.linuxtools.internal.docker.ui.views.DockerContainersContentProvider$1.run(DockerContainersContentProvider.java:64)
> at org.eclipse.core.internal.jobs.Worker.run(Worker.java:55)
> Bundles:
> | org.eclipse.core.jobs | 3.8.0.v20160209-0147 | 3.8.0.v20160209-0147 |
> | org.eclipse.linuxtools.docker.core | 2.0.0.201605161002 | 2.0.0.201605161002 |
> | org.eclipse.linuxtools.docker.ui | 2.0.0.201605161002 | 2.0.0.201605161002 |
> 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/57449... 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-22301) NPE in new OS application from eclipse project with no remote git reference.
by Andre Dietisheim (JIRA)
[ https://issues.jboss.org/browse/JBIDE-22301?page=com.atlassian.jira.plugi... ]
Andre Dietisheim commented on JBIDE-22301:
------------------------------------------
[~scabanovich] can you please look into this?
> NPE in new OS application from eclipse project with no remote git reference.
> ----------------------------------------------------------------------------
>
> Key: JBIDE-22301
> URL: https://issues.jboss.org/browse/JBIDE-22301
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: openshift
> Affects Versions: 4.4.0.Alpha1
> Environment: JBDS 10.0.0.Alpha1
> Reporter: Radim Hopp
> Assignee: Viacheslav Kabanovich
> Fix For: 4.4.0.Alpha2
>
>
> Trying to finish new openshift application wizard using existing aplication from workspace without remote git repository fails with NPE:
> {noformat:title=Unhandled event loop exception}
> java.lang.NullPointerException
> at org.jboss.tools.openshift.internal.ui.wizard.newapp.NewApplicationWizard.performFinish(NewApplicationWizard.java:194)
> at org.eclipse.jface.wizard.WizardDialog.finishPressed(WizardDialog.java:790)
> at org.eclipse.jface.wizard.WizardDialog.buttonPressed(WizardDialog.java:423)
> at org.eclipse.jface.dialogs.Dialog$2.widgetSelected(Dialog.java:618)
> at org.eclipse.swt.widgets.TypedListener.handleEvent(TypedListener.java:248)
> at org.eclipse.swt.widgets.EventTable.sendEvent(EventTable.java:84)
> at org.eclipse.swt.widgets.Display.sendEvent(Display.java:4494)
> at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1339)
> at org.eclipse.swt.widgets.Display.runDeferredEvents(Display.java:3832)
> at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:3443)
> at org.eclipse.jface.window.Window.runEventLoop(Window.java:818)
> at org.eclipse.jface.window.Window.open(Window.java:794)
> at org.jboss.tools.common.ui.WizardUtils.openWizardDialog(WizardUtils.java:287)
> at org.jboss.tools.common.ui.WizardUtils.openWizardDialog(WizardUtils.java:270)
> at org.jboss.tools.openshift.internal.ui.handler.NewApplicationHandler.execute(NewApplicationHandler.java:34)
> at org.eclipse.ui.internal.handlers.HandlerProxy.execute(HandlerProxy.java:295)
> at org.eclipse.ui.internal.handlers.E4HandlerProxy.execute(E4HandlerProxy.java:90)
> 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.e4.core.internal.di.MethodRequestor.execute(MethodRequestor.java:54)
> at org.eclipse.e4.core.internal.di.InjectorImpl.invokeUsingClass(InjectorImpl.java:282)
> at org.eclipse.e4.core.internal.di.InjectorImpl.invoke(InjectorImpl.java:264)
> at org.eclipse.e4.core.contexts.ContextInjectionFactory.invoke(ContextInjectionFactory.java:132)
> at org.eclipse.e4.core.commands.internal.HandlerServiceHandler.execute(HandlerServiceHandler.java:152)
> at org.eclipse.core.commands.Command.executeWithChecks(Command.java:494)
> at org.eclipse.core.commands.ParameterizedCommand.executeWithChecks(ParameterizedCommand.java:491)
> at org.eclipse.e4.core.commands.internal.HandlerServiceImpl.executeHandler(HandlerServiceImpl.java:210)
> at org.eclipse.e4.ui.workbench.renderers.swt.HandledContributionItem.executeItem(HandledContributionItem.java:425)
> at org.eclipse.e4.ui.workbench.renderers.swt.AbstractContributionItem.handleWidgetSelection(AbstractContributionItem.java:449)
> at org.eclipse.e4.ui.workbench.renderers.swt.AbstractContributionItem$3.handleEvent(AbstractContributionItem.java:477)
> at org.eclipse.swt.widgets.EventTable.sendEvent(EventTable.java:84)
> at org.eclipse.swt.widgets.Display.sendEvent(Display.java:4494)
> at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1339)
> at org.eclipse.swt.widgets.Display.runDeferredEvents(Display.java:3832)
> at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:3443)
> at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine$4.run(PartRenderingEngine.java:1118)
> at org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:336)
> at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine.run(PartRenderingEngine.java:1019)
> at org.eclipse.e4.ui.internal.workbench.E4Workbench.createAndRunUI(E4Workbench.java:157)
> at org.eclipse.ui.internal.Workbench$5.run(Workbench.java:691)
> 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:150)
> 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:670)
> at org.eclipse.equinox.launcher.Main.basicRun(Main.java:609)
> at org.eclipse.equinox.launcher.Main.run(Main.java:1516)
> at org.eclipse.equinox.launcher.Main.main(Main.java:1489)
> {noformat}
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 10 months
[JBoss JIRA] (ERT-224) DockerException in DockerConnection.listContainers [EBZ#494871]
by Xavier Coulon (JIRA)
[ https://issues.jboss.org/browse/ERT-224?page=com.atlassian.jira.plugin.sy... ]
Xavier Coulon resolved ERT-224.
-------------------------------
Assignee: Xavier Coulon
Resolution: Done
> DockerException in DockerConnection.listContainers [EBZ#494871]
> ---------------------------------------------------------------
>
> Key: ERT-224
> URL: https://issues.jboss.org/browse/ERT-224
> Project: Eclipse Release Train
> Issue Type: Task
> Components: Linux Tools
> Reporter: Friendly Jira Robot
> Assignee: Xavier Coulon
> Labels: Docker, bzira
>
> The following problem was reported via the automated error reporting:
> Message: Timeout: GET https://192.168.99.101:2376/containers/json?all=1
> org.eclipse.linuxtools.docker.core.DockerException: Timeout: GET https://192.168.99.101:2376/containers/json?all=1
> at org.eclipse.linuxtools.internal.docker.core.DockerConnection.listContainers(DockerConnection.java:635)
> at org.eclipse.linuxtools.internal.docker.core.DockerConnection.getContainers(DockerConnection.java:483)
> at org.eclipse.linuxtools.internal.docker.ui.views.DockerContainersContentProvider$1.run(DockerContainersContentProvider.java:64)
> at org.eclipse.core.internal.jobs.Worker.run(Worker.java:55)
> Bundles:
> | org.eclipse.core.jobs | 3.8.0.v20160209-0147 | 3.8.0.v20160209-0147 |
> | org.eclipse.linuxtools.docker.core | 2.0.0.201605161002 | 2.0.0.201605161002 |
> | org.eclipse.linuxtools.docker.ui | 2.0.0.201605161002 | 2.0.0.201605161002 |
> 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/57449... 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] (JBDS-3918) Latest DevStudio build starts without splash screen
by Denis Golovin (JIRA)
Denis Golovin created JBDS-3918:
-----------------------------------
Summary: Latest DevStudio build starts without splash screen
Key: JBDS-3918
URL: https://issues.jboss.org/browse/JBDS-3918
Project: Red Hat Developer Studio (DevStudio)
Issue Type: Bug
Components: p2-product
Affects Versions: 10.0.0.Alpha3
Environment: OS:
Windows 10
Devstudio:
Version: 10.0.0.Alpha3
Build id: Alpha3-v20160601-0425-B5485
Build date: 20160601-0425
Reporter: Denis Golovin
Latest nightly build downloaded bu Development Suite installer starts without splash screen
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 10 months
[JBoss JIRA] (JBIDE-19506) Connection wizard, Connection: should have unit tests
by Andre Dietisheim (JIRA)
[ https://issues.jboss.org/browse/JBIDE-19506?page=com.atlassian.jira.plugi... ]
Andre Dietisheim edited comment on JBIDE-19506 at 6/1/16 4:08 AM:
------------------------------------------------------------------
quite a few more tests added in [#1199|https://github.com/jbosstools/jbosstools-openshift/pull/1199] even though the coverage is still not where I expect it to be in this very crucial part of the tooling. I thus would merge and postpone to add further tests
was (Author: adietish):
quite a few more tests added in [#1199h|ttps://github.com/jbosstools/jbosstools-openshift/pull/1199] even though the coverage is still not where I expect it to be in this very crucial part of the tooling. I thus would merge and postpone to add further tests
> Connection wizard, Connection: should have unit tests
> ------------------------------------------------------
>
> Key: JBIDE-19506
> URL: https://issues.jboss.org/browse/JBIDE-19506
> Project: Tools (JBoss Tools)
> Issue Type: Enhancement
> Components: openshift
> Affects Versions: 4.3.0.Alpha2
> Reporter: Andre Dietisheim
> Assignee: Andre Dietisheim
> Labels: openshift_v3, tests
> Fix For: 4.4.0.Alpha3
>
> Original Estimate: 2 days
> Time Spent: 2 days
> Remaining Estimate: 2 days
>
> In the new implementation of the connection wizard, that allows v2 and v3 connections (JBIDE-19096) we have rather complex behaviour that we should assert via unit tests.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 10 months