September 2019 - jbosstools-issues

[JBoss JIRA] (JBIDE-24899) Deploy Docker Image wizard: Image not found

by Jeff Johnston (Jira)

[ https://issues.jboss.org/browse/JBIDE-24899?page=com.atlassian.jira.plugi... ] Jeff Johnston commented on JBIDE-24899: --------------------------------------- Hi Andre, while I don't have access to your code, I think I may know the problem. The registry info is only supposed to be used for pushing and pulling (e.g. we need to tag with the registry ahead of a push when pushing to another registry). Using the full-blown registry as part of the name is confusing docker-client for local actions such as getImageInfo(). My suggestion would be to find the image in DockerExplorer's tree (this should be available in the call to the Wizard/dialog from the user selecting it). Once you have the image, you should be able to use its id instead of the "tag with registry" to call getImageInfo(). If pushing to registry you will need to construct a new tag for the push that has the registry plus the desired repo/image name but I'm guessing your code already does that directly or indirectly. > Deploy Docker Image wizard: Image not found > ------------------------------------------- > > Key: JBIDE-24899 > URL: https://issues.jboss.org/browse/JBIDE-24899 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: cdk, docker, openshift > Affects Versions: 4.5.1.AM1 > Reporter: Josef Kopriva > Assignee: André Dietisheim > Priority: Major > Labels: deploy_docker_wizard, openshift_v3 > Fix For: 4.13.0.Final > > Attachments: image-2017-08-29-09-50-20-927.png > > > Exception in Error log: > {code:java} > Failed to inspect image: '172.30.1.1:5000/test/hola:latest' > com.spotify.docker.client.exceptions.ImageNotFoundException: Image not found: 172.30.1.1:5000/test/hola:latest > at com.spotify.docker.client.DefaultDockerClient.inspectImage(DefaultDockerClient.java:1330) > at org.eclipse.linuxtools.internal.docker.core.DockerConnection.getImageInfo(DockerConnection.java:896) > at org.jboss.tools.openshift.internal.ui.wizard.deployimage.DeployImageWizardModel.lookupImageMetadata(DeployImageWizardModel.java:655) > at org.jboss.tools.openshift.internal.ui.wizard.deployimage.DeployImageWizardModel.initializeContainerInfo(DeployImageWizardModel.java:354) > at org.jboss.tools.openshift.internal.ui.wizard.deployimage.DeployImagePage$1ImageValidatorJob.run(DeployImagePage.java:154) > at org.eclipse.core.internal.jobs.Worker.run(Worker.java:56) > Caused by: com.spotify.docker.client.exceptions.DockerRequestException: Request error: GET https://192.168.42.121:2376/images/172.30.1.1:5000/test/hola:latest/json: 404 > at com.spotify.docker.client.DefaultDockerClient.propagate(DefaultDockerClient.java:2084) > at com.spotify.docker.client.DefaultDockerClient.request(DefaultDockerClient.java:2023) > at com.spotify.docker.client.DefaultDockerClient.inspectImage(DefaultDockerClient.java:1326) > ... 5 more > Caused by: javax.ws.rs.NotFoundException: HTTP 404 Not Found > at org.glassfish.jersey.client.JerseyInvocation.convertToException(JerseyInvocation.java:1008) > at org.glassfish.jersey.client.JerseyInvocation.translate(JerseyInvocation.java:816) > at org.glassfish.jersey.client.JerseyInvocation.access$700(JerseyInvocation.java:92) > at org.glassfish.jersey.client.JerseyInvocation$5.completed(JerseyInvocation.java:773) > at org.glassfish.jersey.client.ClientRuntime.processResponse(ClientRuntime.java:198) > at org.glassfish.jersey.client.ClientRuntime.access$300(ClientRuntime.java:79) > at org.glassfish.jersey.client.ClientRuntime$2.run(ClientRuntime.java:180) > at org.glassfish.jersey.internal.Errors$1.call(Errors.java:271) > at org.glassfish.jersey.internal.Errors$1.call(Errors.java:267) > at org.glassfish.jersey.internal.Errors.process(Errors.java:315) > at org.glassfish.jersey.internal.Errors.process(Errors.java:297) > at org.glassfish.jersey.internal.Errors.process(Errors.java:267) > at org.glassfish.jersey.process.internal.RequestScope.runInScope(RequestScope.java:340) > at org.glassfish.jersey.client.ClientRuntime$3.run(ClientRuntime.java:210) > at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511) > at java.util.concurrent.FutureTask.run(FutureTask.java:266) > at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149) > at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624) > at java.lang.Thread.run(Thread.java:748) > eclipse.buildId=11.1.0.AM1-v20170824-1835-B873 > java.version=1.8.0_141 > java.vendor=Oracle Corporation > BootLoader constants: OS=linux, ARCH=x86_64, WS=gtk, NL=en_US > Framework arguments: -product com.jboss.devstudio.core.product > Command-line arguments: -os linux -ws gtk -arch x86_64 -product com.jboss.devstudio.core.product > {code} -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 6 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-26870) Use wildwestdeveloper/chromedebugger replacing outdated chromedevtools

by André Dietisheim (Jira)

[ https://issues.jboss.org/browse/JBIDE-26870?page=com.atlassian.jira.plugi... ] André Dietisheim updated JBIDE-26870: ------------------------------------- Description: In JBIDE-26408 it has been stated that the chromedevtools only [support up to NodeJS 7|https://issues.jboss.org/browse/JBIDE-26408?focusedCommentId=13750500&p...] and are deprecated/not being worked on any more. See https://bugs.eclipse.org/bugs/show_bug.cgi?id=537907 for more details. We should replace these and use the chrome debugger in wildwestdeveloper instead: see https://github.com/eclipse/wildwebdeveloper/issues/230 was: In JBIDE-26408 it has been stated that the chromedevtools only [support up to NodeJS 7](https://issues.jboss.org/browse/JBIDE-26408?focusedCommentId=13750500&... and are deprecated/not being worked on any more. See https://bugs.eclipse.org/bugs/show_bug.cgi?id=537907 for more details. We should replace these and use the chrome debugger in wildwestdeveloper instead: see https://github.com/eclipse/wildwebdeveloper/issues/230 > Use wildwestdeveloper/chromedebugger replacing outdated chromedevtools > ---------------------------------------------------------------------- > > Key: JBIDE-26870 > URL: https://issues.jboss.org/browse/JBIDE-26870 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: openshift > Affects Versions: 4.13.0.AM1 > Reporter: André Dietisheim > Priority: Major > Fix For: 4.14.x > > > In JBIDE-26408 it has been stated that the chromedevtools only [support up to NodeJS 7|https://issues.jboss.org/browse/JBIDE-26408?focusedCommentId=13750500&p...] and are deprecated/not being worked on any more. > See https://bugs.eclipse.org/bugs/show_bug.cgi?id=537907 for more details. > We should replace these and use the chrome debugger in wildwestdeveloper instead: see https://github.com/eclipse/wildwebdeveloper/issues/230 -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 6 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-26870) Use wildwestdeveloper/chromedebugger replacing outdated chromedevtools

by André Dietisheim (Jira)

[ https://issues.jboss.org/browse/JBIDE-26870?page=com.atlassian.jira.plugi... ] André Dietisheim updated JBIDE-26870: ------------------------------------- Description: In JBIDE-26408 it has been stated that the chromedevtools only [support up to NodeJS 7](https://issues.jboss.org/browse/JBIDE-26408?focusedCommentId=13750500&... and are deprecated/not being worked on any more. See https://bugs.eclipse.org/bugs/show_bug.cgi?id=537907 for more details. We should replace these and use the chrome debugger in wildwestdeveloper instead: see https://github.com/eclipse/wildwebdeveloper/issues/230 was: In JBIDE-26408 it has been stated that the chromedevtools only support up to NodeJS 7 and are deprecated/not being worked on any more. See here: https://issues.jboss.org/browse/JBIDE-26408?focusedCommentId=13750500&pag... See https://bugs.eclipse.org/bugs/show_bug.cgi?id=537907 for more details. We should replace these and use the chrome debugger in wildwestdeveloper instead: see https://github.com/eclipse/wildwebdeveloper/issues/230 > Use wildwestdeveloper/chromedebugger replacing outdated chromedevtools > ---------------------------------------------------------------------- > > Key: JBIDE-26870 > URL: https://issues.jboss.org/browse/JBIDE-26870 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: openshift > Affects Versions: 4.13.0.AM1 > Reporter: André Dietisheim > Priority: Major > Fix For: 4.14.x > > > In JBIDE-26408 it has been stated that the chromedevtools only [support up to NodeJS 7](https://issues.jboss.org/browse/JBIDE-26408?focusedCommentId=13750500&... and are deprecated/not being worked on any more. > See https://bugs.eclipse.org/bugs/show_bug.cgi?id=537907 for more details. > We should replace these and use the chrome debugger in wildwestdeveloper instead: see https://github.com/eclipse/wildwebdeveloper/issues/230 -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 6 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-26870) Use wildwestdeveloper/chromedebugger replacing outdated chromedevtools

by André Dietisheim (Jira)

[ https://issues.jboss.org/browse/JBIDE-26870?page=com.atlassian.jira.plugi... ] André Dietisheim updated JBIDE-26870: ------------------------------------- Description: In JBIDE-26408 it has been stated that the chromedevtools only support up to NodeJS 7 and are deprecated/not being worked on any more. See here: https://issues.jboss.org/browse/JBIDE-26408?focusedCommentId=13750500&pag... See https://bugs.eclipse.org/bugs/show_bug.cgi?id=537907 for more details. We should replace these and use the chrome debugger in wildwestdeveloper instead: see https://github.com/eclipse/wildwebdeveloper/issues/230 was: In JBIDE-26408 it has been stated that the chromedevtools only support up to NodeJS 7 and are deprecated/not being worked on any more. See https://bugs.eclipse.org/bugs/show_bug.cgi?id=537907 for more details. We should replace these and use the chrome debugger in wildwestdeveloper instead: see https://github.com/eclipse/wildwebdeveloper/issues/230 > Use wildwestdeveloper/chromedebugger replacing outdated chromedevtools > ---------------------------------------------------------------------- > > Key: JBIDE-26870 > URL: https://issues.jboss.org/browse/JBIDE-26870 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: openshift > Affects Versions: 4.13.0.AM1 > Reporter: André Dietisheim > Priority: Major > Fix For: 4.14.x > > > In JBIDE-26408 it has been stated that the chromedevtools only support up to NodeJS 7 and are deprecated/not being worked on any more. See here: https://issues.jboss.org/browse/JBIDE-26408?focusedCommentId=13750500&pag... > See https://bugs.eclipse.org/bugs/show_bug.cgi?id=537907 for more details. > We should replace these and use the chrome debugger in wildwestdeveloper instead: see https://github.com/eclipse/wildwebdeveloper/issues/230 -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 6 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-26870) Use wildwestdeveloper/chromedebugger replacing outdated chromedevtools

by André Dietisheim (Jira)

[ https://issues.jboss.org/browse/JBIDE-26870?page=com.atlassian.jira.plugi... ] André Dietisheim updated JBIDE-26870: ------------------------------------- Fix Version/s: 4.14.x > Use wildwestdeveloper/chromedebugger replacing outdated chromedevtools > ---------------------------------------------------------------------- > > Key: JBIDE-26870 > URL: https://issues.jboss.org/browse/JBIDE-26870 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: openshift > Affects Versions: 4.13.0.AM1 > Reporter: André Dietisheim > Priority: Major > Fix For: 4.14.x > > > In JBIDE-26408 it has been stated that the chromedevtools only support up to NodeJS 7 and are deprecated/not being worked on any more. > See https://bugs.eclipse.org/bugs/show_bug.cgi?id=537907 for more details. > We should replace these and use the chrome debugger in wildwestdeveloper instead: see https://github.com/eclipse/wildwebdeveloper/issues/230 -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 6 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-26870) Use wildwestdeveloper/chromedebugger replacing outdated chromedevtools

by André Dietisheim (Jira)

André Dietisheim created JBIDE-26870: ---------------------------------------- Summary: Use wildwestdeveloper/chromedebugger replacing outdated chromedevtools Key: JBIDE-26870 URL: https://issues.jboss.org/browse/JBIDE-26870 Project: Tools (JBoss Tools) Issue Type: Feature Request Components: openshift Affects Versions: 4.13.0.AM1 Reporter: André Dietisheim In JBIDE-26408 it has been stated that the chromedevtools only support up to NodeJS 7 and are deprecated/not being worked on any more. See https://bugs.eclipse.org/bugs/show_bug.cgi?id=537907 for more details. We should replace these and use the chrome debugger in wildwestdeveloper instead: see https://github.com/eclipse/wildwebdeveloper/issues/230 -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 6 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-26844) Update WF18 support to WF18 GA

by Mohit Suman (Jira)

[ https://issues.jboss.org/browse/JBIDE-26844?page=com.atlassian.jira.plugi... ] Mohit Suman updated JBIDE-26844: -------------------------------- Story Points: 2 > Update WF18 support to WF18 GA > ------------------------------ > > Key: JBIDE-26844 > URL: https://issues.jboss.org/browse/JBIDE-26844 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: server > Affects Versions: 4.13.0.AM1 > Reporter: Jeff MAURY > Assignee: Jeff MAURY > Priority: Major > Fix For: 4.13.0.Final > > -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 6 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-26408) [UPSTREAM] Server adapter: debugging fails for nodejs-mongo-persistent template based application

by André Dietisheim (Jira)

[ https://issues.jboss.org/browse/JBIDE-26408?page=com.atlassian.jira.plugi... ] André Dietisheim updated JBIDE-26408: ------------------------------------- Comment: was deleted (was: [~jeffmaury] can you please add 4.13.x fixVersion? This needs to be kept open to track upstream developement in Eclipse (or the lack thereof).) > [UPSTREAM] Server adapter: debugging fails for nodejs-mongo-persistent template based application > ------------------------------------------------------------------------------------------------- > > Key: JBIDE-26408 > URL: https://issues.jboss.org/browse/JBIDE-26408 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.9.0.Final > Environment: cdk-3.6.0+ > Reporter: André Dietisheim > Assignee: Jeff MAURY > Priority: Major > Labels: node, server_adapter, upstream > Fix For: 4.14.x > > Attachments: change-nodejs-version.png, screenshot-1.png, screenshot-2.png > > > steps: > # ASSERT: have cdk 3.6.0 > # EXEC: create an application based on the *nodejs-mongo-persistent* template, have the application imported to the workspace and the server adapter created for it > # EXEC: start the server adapter > # ASSERT: server adapter is *[Started, Synchronized]* > # EXEC: Restart the adapter into debugging > Result: > You very quickly (the timeout seems very short) get an error dialog telling you that the debugger could not connect. > !screenshot-1.png! > The debugger is therefore stopped, debugging wont work. > !screenshot-2.png! > Trying to restart it reproduces the error that we already have. > In the Eclipse log you'll find the following: > {code} > java.io.IOException: Timed out waiting for handshake > at org.eclipse.wst.jsdt.chromium.internal.v8native.JavascriptVmImpl.newIOException(JavascriptVmImpl.java:114) > at org.eclipse.wst.jsdt.chromium.internal.standalonev8.StandaloneVmImpl.attachImpl(StandaloneVmImpl.java:134) > at org.eclipse.wst.jsdt.chromium.internal.standalonev8.StandaloneVmImpl.attach(StandaloneVmImpl.java:79) > at org.eclipse.wst.jsdt.chromium.debug.core.model.JavascriptVmEmbedderFactory$4$1.attach(JavascriptVmEmbedderFactory.java:207) > at org.eclipse.wst.jsdt.chromium.debug.core.model.DebugTargetImpl.attach(DebugTargetImpl.java:74) > at org.eclipse.wst.jsdt.chromium.debug.ui.launcher.LaunchTypeBase.launch(LaunchTypeBase.java:101) > at org.eclipse.debug.internal.core.LaunchConfiguration.launch(LaunchConfiguration.java:859) > at org.eclipse.debug.internal.core.LaunchConfiguration.launch(LaunchConfiguration.java:717) > at org.eclipse.debug.internal.ui.DebugUIPlugin.buildAndLaunch(DebugUIPlugin.java:1026) > at org.eclipse.debug.internal.ui.DebugUIPlugin$2.run(DebugUIPlugin.java:1240) > at org.eclipse.core.internal.jobs.Worker.run(Worker.java:60) > Caused by: java.util.concurrent.TimeoutException > at java.base/java.util.concurrent.FutureTask.get(FutureTask.java:204) > at org.eclipse.wst.jsdt.chromium.internal.standalonev8.StandaloneVmImpl.attachImpl(StandaloneVmImpl.java:127) > ... 9 more > {code} -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 6 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-26818) Installing nodeclipse presents remediation page

by André Dietisheim (Jira)

[ https://issues.jboss.org/browse/JBIDE-26818?page=com.atlassian.jira.plugi... ] André Dietisheim updated JBIDE-26818: ------------------------------------- Summary: Installing nodeclipse presents remediation page (was: Installing nodeclipse errors) > Installing nodeclipse presents remediation page > ----------------------------------------------- > > Key: JBIDE-26818 > URL: https://issues.jboss.org/browse/JBIDE-26818 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: central > Affects Versions: 4.12.0.Final > Reporter: André Dietisheim > Priority: Major > Fix For: 4.13.0.Final > > Attachments: image-2019-09-09-20-45-46-479.png, installation-cannot-proceed-alternative.png > > > steps: > # ASSERT: have "Software/Update" tab of central editor opened > # EXEC: choose nodeclise and hit "Install/Update" > Result: > Nodeclipse cannot be installed. And error is displayed > !image-2019-09-09-20-45-46-479.png! -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 6 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-26817) link to "Get involved" shows the page for CAT that was suspended in 2016

by Jeff MAURY (Jira)

[ https://issues.jboss.org/browse/JBIDE-26817?page=com.atlassian.jira.plugi... ] Jeff MAURY commented on JBIDE-26817: ------------------------------------ Maybe a deployment of the updated Central page and update to ide-config.properties ? > link to "Get involved" shows the page for CAT that was suspended in 2016 > ------------------------------------------------------------------------ > > Key: JBIDE-26817 > URL: https://issues.jboss.org/browse/JBIDE-26817 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: central > Affects Versions: 4.12.0.Final > Reporter: André Dietisheim > Assignee: André Dietisheim > Priority: Major > Fix For: 4.13.0.Final > > Attachments: image-2019-09-09-21-39-10-326.png, image-2019-09-09-21-40-21-204.png, image-2019-09-11-17-34-37-623.png, issue.png > > > steps: > # ASSERT: have central opened > # EXEC: click on the link "Get involved" > !image-2019-09-09-21-39-10-326.png! > result: > browser is opened displaying the page for the [CAT program|https://tools.jboss.org/cat/] that was suspended in *2016* > !image-2019-09-09-21-40-21-204.png! -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 6 months

1
0
0 / 0

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jbosstools-issues September 2019