July 2019 - jbosstools-issues - Jboss List Archives

[JBoss JIRA] (JBIDE-26641) Connect wizard: cancelling certificate keeps dialog blank

by André Dietisheim (Jira)

[ https://issues.jboss.org/browse/JBIDE-26641?page=com.atlassian.jira.plugi... ] André Dietisheim updated JBIDE-26641: ------------------------------------- Labels: connection_wizard (was: ) > Connect wizard: cancelling certificate keeps dialog blank > --------------------------------------------------------- > > Key: JBIDE-26641 > URL: https://issues.jboss.org/browse/JBIDE-26641 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.12.0.AM1 > Reporter: André Dietisheim > Priority: Major > Labels: connection_wizard > Fix For: 4.12.x > > Attachments: image-2019-05-10-15-37-51-433.png > > > steps: > # EXEC: launch connection wizard and try to create a new connection > # EXEC: as Server use "https://open.paas.redhat.com" > # EXEC: hit "retrieve" link in the "Authentication" group > # ASSERT. dialog pops up where you'll be able to retrieve a token but before that also a dialog that warns of a untrusted/self-signed certificate > # EXEC: hit "Cancel" aka refuse to trust the certificate > Result: > The dialog where the page to retrieve a token would be displayed stays open and blank > !image-2019-05-10-15-37-51-433.png! -- This message was sent by Atlassian Jira (v7.12.1#712002)

6 years, 9 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-26638) Import app: error message is not clearly matching available options

by André Dietisheim (Jira)

[ https://issues.jboss.org/browse/JBIDE-26638?page=com.atlassian.jira.plugi... ] André Dietisheim updated JBIDE-26638: ------------------------------------- Priority: Minor (was: Major) > Import app: error message is not clearly matching available options > -------------------------------------------------------------------- > > Key: JBIDE-26638 > URL: https://issues.jboss.org/browse/JBIDE-26638 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: openshift > Affects Versions: 4.12.0.AM1 > Reporter: André Dietisheim > Priority: Minor > Labels: import_wizard > Fix For: 4.12.x > > Attachments: image-2019-05-07-22-20-07-049.png > > > steps: > # ASSERT: have an application running on OpenShift > # ASSERT: have it imported a 1st time > # EXEC: kill the application & create it again > # ASSERT: import application wizard pops up so that you can import it but it's displaying an error that tells you that the git clone already exists > Result: > !image-2019-05-07-22-20-07-049.png! > The error message states that the git clone already exists and tells you to *select Reuse existing repository*. In the GUI though there's no such option, there's a checkbox marked with an error that's called *Do not clone - use existing repository* > Expected result: > The error message should matcht the label of the checkbox so that it gets more obvious what option is suggested. ex. *select use existing repository* -- This message was sent by Atlassian Jira (v7.12.1#712002)

6 years, 9 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-26638) Import app: error message is not clearly matching available options

by André Dietisheim (Jira)

[ https://issues.jboss.org/browse/JBIDE-26638?page=com.atlassian.jira.plugi... ] André Dietisheim updated JBIDE-26638: ------------------------------------- Labels: import_wizard (was: ) > Import app: error message is not clearly matching available options > -------------------------------------------------------------------- > > Key: JBIDE-26638 > URL: https://issues.jboss.org/browse/JBIDE-26638 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: openshift > Affects Versions: 4.12.0.AM1 > Reporter: André Dietisheim > Priority: Minor > Labels: import_wizard > Fix For: 4.12.x > > Attachments: image-2019-05-07-22-20-07-049.png > > > steps: > # ASSERT: have an application running on OpenShift > # ASSERT: have it imported a 1st time > # EXEC: kill the application & create it again > # ASSERT: import application wizard pops up so that you can import it but it's displaying an error that tells you that the git clone already exists > Result: > !image-2019-05-07-22-20-07-049.png! > The error message states that the git clone already exists and tells you to *select Reuse existing repository*. In the GUI though there's no such option, there's a checkbox marked with an error that's called *Do not clone - use existing repository* > Expected result: > The error message should matcht the label of the checkbox so that it gets more obvious what option is suggested. ex. *select use existing repository* -- This message was sent by Atlassian Jira (v7.12.1#712002)

6 years, 9 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-26659) Server: Cannot download WF17 via new runtime dialog

by André Dietisheim (Jira)

[ https://issues.jboss.org/browse/JBIDE-26659?page=com.atlassian.jira.plugi... ] André Dietisheim edited comment on JBIDE-26659 at 7/2/19 6:26 PM: ------------------------------------------------------------------ [~jkopriva] This now works for me. Downloading wfl17 works fine (since it was released in the meantime). Resolving as CANNOT_REPRODUCE since it now works. Please reopen if this doesn't work for you. was (Author: adietish): [~jkopriva] This now works for me. Downloading wfl17 works fine. Resolving as WORKS_AS_EXPECTED. Please reopen if this doesnt work for you. > Server: Cannot download WF17 via new runtime dialog > --------------------------------------------------- > > Key: JBIDE-26659 > URL: https://issues.jboss.org/browse/JBIDE-26659 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: server > Affects Versions: 4.12.0.AM1 > Reporter: Josef Kopriva > Assignee: André Dietisheim > Priority: Major > Fix For: 4.12.0.Final > > -- This message was sent by Atlassian Jira (v7.12.1#712002)

6 years, 9 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-26659) Server: Cannot download WF17 via new runtime dialog

by André Dietisheim (Jira)

[ https://issues.jboss.org/browse/JBIDE-26659?page=com.atlassian.jira.plugi... ] André Dietisheim resolved JBIDE-26659. -------------------------------------- Assignee: André Dietisheim Resolution: Cannot Reproduce > Server: Cannot download WF17 via new runtime dialog > --------------------------------------------------- > > Key: JBIDE-26659 > URL: https://issues.jboss.org/browse/JBIDE-26659 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: server > Affects Versions: 4.12.0.AM1 > Reporter: Josef Kopriva > Assignee: André Dietisheim > Priority: Major > Fix For: 4.12.0.Final > > -- This message was sent by Atlassian Jira (v7.12.1#712002)

6 years, 9 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-26659) Server: Cannot download WF17 via new runtime dialog

by André Dietisheim (Jira)

[ https://issues.jboss.org/browse/JBIDE-26659?page=com.atlassian.jira.plugi... ] André Dietisheim edited comment on JBIDE-26659 at 7/2/19 6:22 PM: ------------------------------------------------------------------ [~jkopriva] This now works for me. Downloading wfl17 works fine. Resolving as WORKS_AS_EXPECTED. Please reopen if this doesnt work for you. was (Author: adietish): [~jkopriva] I guess that this now works fine, can you please confirm? > Server: Cannot download WF17 via new runtime dialog > --------------------------------------------------- > > Key: JBIDE-26659 > URL: https://issues.jboss.org/browse/JBIDE-26659 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: server > Affects Versions: 4.12.0.AM1 > Reporter: Josef Kopriva > Priority: Major > Fix For: 4.12.0.Final > > -- This message was sent by Atlassian Jira (v7.12.1#712002)

6 years, 9 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-26659) Server: Cannot download WF17 via new runtime dialog

by André Dietisheim (Jira)

[ https://issues.jboss.org/browse/JBIDE-26659?page=com.atlassian.jira.plugi... ] André Dietisheim commented on JBIDE-26659: ------------------------------------------ [~jkopriva] I guess that this now works fine, can you please confirm? > Server: Cannot download WF17 via new runtime dialog > --------------------------------------------------- > > Key: JBIDE-26659 > URL: https://issues.jboss.org/browse/JBIDE-26659 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: server > Affects Versions: 4.12.0.AM1 > Reporter: Josef Kopriva > Priority: Major > Fix For: 4.12.0.Final > > -- This message was sent by Atlassian Jira (v7.12.1#712002)

6 years, 9 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-25992) FileNotFoundException: org.jboss.tools.as.itests.CreateServerCheckDefaultsTestorg.jboss.ide.eclipse.as.wildfly.80/xpaths.xml (No such file or directory)

by André Dietisheim (Jira)

[ https://issues.jboss.org/browse/JBIDE-25992?page=com.atlassian.jira.plugi... ] André Dietisheim resolved JBIDE-25992. -------------------------------------- Resolution: Out of Date > FileNotFoundException: org.jboss.tools.as.itests.CreateServerCheckDefaultsTestorg.jboss.ide.eclipse.as.wildfly.80/xpaths.xml (No such file or directory) > -------------------------------------------------------------------------------------------------------------------------------------------------------- > > Key: JBIDE-25992 > URL: https://issues.jboss.org/browse/JBIDE-25992 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: integration-tests, server > Affects Versions: 4.6.0.AM1 > Reporter: Nick Boldt > Assignee: Rob Stryker > Priority: Major > Fix For: 4.12.0.Final > > > Server.it.weekly jobs are failing because of this error in the console log: > {code} > java.io.FileNotFoundException: /mnt/hudson_workspace/workspace/server.it.weekly/f623f724/as/itests/org.jboss.tools.as.itests/target/ > work/data/.metadata/.plugins/org.jboss.ide.eclipse.as.core/ > org.jboss.tools.as.itests.CreateServerCheckDefaultsTestorg.jboss.ide.eclipse.as.wildfly.80/xpaths.xml (No such file or directory) > {code} -- https://dev-platform-jenkins.rhev-ci-vms.eng.rdu2.redhat.com/job/server.i... > If this is a normal, expected exception, then I can exclude if from the console parser [1]. > If not, then it should be fixed. -- This message was sent by Atlassian Jira (v7.12.1#712002)

6 years, 9 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 commented on JBIDE-26408: ------------------------------------------ this doesn't exist any more in current itests output (which also fails with lots of error). I'll thus close as OUTDATED. > [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.12.0.Final > > 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.12.1#712002)

6 years, 9 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 commented on JBIDE-26408: ------------------------------------------ [~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.12.0.Final > > 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.12.1#712002)

6 years, 9 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 July 2019