[JBoss JIRA] (ERT-379) Exceptions while expanding Variables view [EBZ#499600]
by Friendly Jira Robot (JIRA)
Friendly Jira Robot created ERT-379:
---------------------------------------
Summary: Exceptions while expanding Variables view [EBZ#499600]
Key: ERT-379
URL: https://issues.jboss.org/browse/ERT-379
Project: Eclipse Release Train
Issue Type: Task
Components: JSDT
Reporter: Friendly Jira Robot
Fix For: Neon.1 (4.6)
Steps to reproduce:
-------------------
1) import: https://github.com/ibuziuk/myRESTApp
2) server.js -> Debug As -> Node.js Application
3) Expand various items variables view.
Stack trace:
================================================
org.eclipse.wst.jsdt.chromium.internal.protocolparser.implutil.CommonImpl$ParseRuntimeException: On demand parsing failed for {"ref":118,"propertyType":2,"attributes":7}
at org.eclipse.wst.jsdt.chromium.internal.protocolparser.dynamicimpl.DynamicParserImpl$LazyParseFieldMethodHandler.handle(DynamicParserImpl.java:696)
at org.eclipse.wst.jsdt.chromium.internal.protocolparser.dynamicimpl.JsonInvocationHandler.invoke(JsonInvocationHandler.java:35)
at com.sun.proxy.$Proxy88.name(Unknown Source)
at org.eclipse.wst.jsdt.chromium.internal.v8native.protocol.V8ProtocolUtil$PropertyNameGetter$SubpropertyNameGetter.getName(V8ProtocolUtil.java:216)
at org.eclipse.wst.jsdt.chromium.internal.v8native.protocol.V8ProtocolUtil$PropertyNameGetter$SubpropertyNameGetter.getName(V8ProtocolUtil.java:1)
at org.eclipse.wst.jsdt.chromium.internal.v8native.protocol.V8ProtocolUtil.extractProperty(V8ProtocolUtil.java:150)
at org.eclipse.wst.jsdt.chromium.internal.v8native.protocol.V8ProtocolUtil.putMirror(V8ProtocolUtil.java:134)
at org.eclipse.wst.jsdt.chromium.internal.v8native.protocol.V8ProtocolUtil.extractObjectProperties(V8ProtocolUtil.java:94)
at org.eclipse.wst.jsdt.chromium.internal.v8native.value.SubpropertiesMirror$JsonBased.getProperties(SubpropertiesMirror.java:69)
at org.eclipse.wst.jsdt.chromium.internal.v8native.value.JsObjectBase$1.runSync(JsObjectBase.java:176)
at org.eclipse.wst.jsdt.chromium.util.AsyncFuture$SyncOperation.execute(AsyncFuture.java:171)
at org.eclipse.wst.jsdt.chromium.internal.v8native.value.JsObjectBase.startPropertyLoadOperation(JsObjectBase.java:199)
at org.eclipse.wst.jsdt.chromium.internal.v8native.value.JsObjectBase.getPropertyData(JsObjectBase.java:138)
at org.eclipse.wst.jsdt.chromium.internal.v8native.value.JsObjectBase.getBasicPropertyData(JsObjectBase.java:159)
at org.eclipse.wst.jsdt.chromium.internal.v8native.value.JsFunctionImpl.getAdditionalPropertyData(JsFunctionImpl.java:82)
at org.eclipse.wst.jsdt.chromium.internal.v8native.value.JsFunctionImpl.getVariableScopes(JsFunctionImpl.java:47)
at org.eclipse.wst.jsdt.chromium.internal.v8native.value.JsFunctionImpl.access$2(JsFunctionImpl.java:46)
at org.eclipse.wst.jsdt.chromium.internal.v8native.value.JsFunctionImpl$1.getScopes(JsFunctionImpl.java:127)
at org.eclipse.wst.jsdt.chromium.debug.core.model.Value.calculateFunctionScopesVariable(Value.java:95)
at org.eclipse.wst.jsdt.chromium.debug.core.model.Value.calculateVariables(Value.java:74)
at org.eclipse.wst.jsdt.chromium.debug.core.model.ValueBase$ValueWithLazyVariables.getVariables(ValueBase.java:77)
at org.eclipse.debug.internal.ui.model.elements.VariableContentProvider.getValueChildren(VariableContentProvider.java:170)
at org.eclipse.debug.internal.ui.model.elements.VariableContentProvider.getAllChildren(VariableContentProvider.java:87)
at org.eclipse.debug.internal.ui.model.elements.VariableContentProvider.getChildCount(VariableContentProvider.java:49)
at org.eclipse.debug.internal.ui.model.elements.ElementContentProvider.retrieveChildCount(ElementContentProvider.java:118)
at org.eclipse.debug.internal.ui.model.elements.ElementContentProvider$2.run(ElementContentProvider.java:67)
at org.eclipse.core.internal.jobs.Worker.run(Worker.java:55)
Caused by: org.eclipse.wst.jsdt.chromium.internal.protocolparser.JsonProtocolParseException: Field is not optional: name (in type org.eclipse.wst.jsdt.chromium.internal.v8native.protocol.input.data.PropertyObject)
at org.eclipse.wst.jsdt.chromium.internal.protocolparser.dynamicimpl.DynamicParserImpl$LazyParseFieldMethodHandler.parse(DynamicParserImpl.java:729)
at org.eclipse.wst.jsdt.chromium.internal.protocolparser.dynamicimpl.DynamicParserImpl$LazyParseFieldMethodHandler.parse(DynamicParserImpl.java:715)
at org.eclipse.wst.jsdt.chromium.internal.protocolparser.dynamicimpl.DynamicParserImpl$LazyParseFieldMethodHandler.handle(DynamicParserImpl.java:694)
... 26 more
================================================
java.lang.NullPointerException
at org.eclipse.wst.jsdt.chromium.internal.v8native.value.JsFunctionImpl.getAdditionalPropertyData(JsFunctionImpl.java:82)
at org.eclipse.wst.jsdt.chromium.internal.v8native.value.JsFunctionImpl.getVariableScopes(JsFunctionImpl.java:47)
at org.eclipse.wst.jsdt.chromium.internal.v8native.value.JsFunctionImpl.access$2(JsFunctionImpl.java:46)
at org.eclipse.wst.jsdt.chromium.internal.v8native.value.JsFunctionImpl$1.getScopes(JsFunctionImpl.java:127)
at org.eclipse.wst.jsdt.chromium.debug.core.model.Value.calculateFunctionScopesVariable(Value.java:95)
at org.eclipse.wst.jsdt.chromium.debug.core.model.Value.calculateVariables(Value.java:74)
at org.eclipse.wst.jsdt.chromium.debug.core.model.ValueBase$ValueWithLazyVariables.getVariables(ValueBase.java:77)
at org.eclipse.debug.internal.ui.model.elements.VariableContentProvider.getValueChildren(VariableContentProvider.java:170)
at org.eclipse.debug.internal.ui.model.elements.VariableContentProvider.getAllChildren(VariableContentProvider.java:87)
at org.eclipse.debug.internal.ui.model.elements.VariableContentProvider.getChildren(VariableContentProvider.java:57)
at org.eclipse.debug.internal.ui.model.elements.ElementContentProvider.retrieveChildren(ElementContentProvider.java:91)
at org.eclipse.debug.internal.ui.model.elements.ElementContentProvider$1.run(ElementContentProvider.java:44)
at org.eclipse.core.internal.jobs.Worker.run(Worker.java:55)
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 8 months
[JBoss JIRA] (JBDS-3995) CDK fails on landrush vagrant plugin installation
by Jan Richter (JIRA)
[ https://issues.jboss.org/browse/JBDS-3995?page=com.atlassian.jira.plugin.... ]
Jan Richter updated JBDS-3995:
------------------------------
Fix Version/s: 10.1.0.AM3
> CDK fails on landrush vagrant plugin installation
> -------------------------------------------------
>
> Key: JBDS-3995
> URL: https://issues.jboss.org/browse/JBDS-3995
> Project: Red Hat JBoss Developer Studio (devstudio)
> Issue Type: Bug
> Components: platform-installer
> Affects Versions: 10.1.0.AM3
> Reporter: Jan Richter
> Assignee: Denis Golovin
> Priority: Blocker
> Fix For: 10.1.0.AM3
>
>
> CDK fails to install during the vagrant plugin installation phase.
> The error:
> {noformat}
> Thu, 11 Aug 2016 07:35:54 GMT-ERROR: cdk - Error: Command failed: vagrant plugin install landrush
> 'vagrant' is not recognized as an internal or external command,
> operable program or batch file.
> Thu, 11 Aug 2016 07:35:54 GMT-ERROR: cdk - 'vagrant' is not recognized as an internal or external command,
> operable program or batch file.
> {noformat}
> Looks like the command is being called without the appropriate environment options.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 8 months
[JBoss JIRA] (JBIDE-22674) Refresh handler throws NPE when no active part are selected
by Marián Labuda (JIRA)
[ https://issues.jboss.org/browse/JBIDE-22674?page=com.atlassian.jira.plugi... ]
Marián Labuda commented on JBIDE-22674:
---------------------------------------
What has been done here? I am not able to reproduce and I see issue as resolved although there is no linked PR.
> Refresh handler throws NPE when no active part are selected
> -----------------------------------------------------------
>
> Key: JBIDE-22674
> URL: https://issues.jboss.org/browse/JBIDE-22674
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: openshift
> Affects Versions: 4.4.0.Final
> Reporter: Jeff MAURY
> Assignee: Jeff MAURY
> Fix For: 4.4.1.AM3
>
>
> EXEC: start Eclipse but don't select any part
> EXEC: unfold an OS3 connection
> EXEC: fill the credentials dialog
> EXEC: Refresh the OS3 connection
> ASSERT: the refresh handler throws NPE in the Eclipse log
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 8 months
[JBoss JIRA] (JBIDE-22603) Sometimes multiple OpenShift watch managers are periodically created and finished
by Marián Labuda (JIRA)
[ https://issues.jboss.org/browse/JBIDE-22603?page=com.atlassian.jira.plugi... ]
Marián Labuda closed JBIDE-22603.
---------------------------------
Verified in DevStudio 10.1.0.AM3 build ID AM3-v20160812-0415-B5753.
> Sometimes multiple OpenShift watch managers are periodically created and finished
> ---------------------------------------------------------------------------------
>
> Key: JBIDE-22603
> URL: https://issues.jboss.org/browse/JBIDE-22603
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: openshift
> Affects Versions: 4.4.0.Final
> Reporter: Marián Labuda
> Assignee: Jeff MAURY
> Priority: Blocker
> Labels: explorer, openshift_v3
> Fix For: 4.4.1.AM3
>
> Attachments: openshift_watchers.ogv, watchers.log, watchers.png
>
>
> Sometimes when I am working with OpenShift toolings, there are created multiple OpenShift Watch Managers which are getting finished, disappearing from Progress view and another new ones are created and this repeats nonstop. Sometimes there are 2-3 running, sometimes even more. I am working with openshift-dev user, where is visible default project (still, until patch in upstream get effect) and my own project with application created from eap 6.4 basic s2i template.
> !watchers.png!
> It would not be a problem but I have a hunch it is the problem breaking automatic update of OpenShift explorer view to reflect current state and existence of resources on OpenShift server. E.g. under a service there is build table visible all the time and no application pod is shown, even build is finished and there is an application pod running on OpenShift. Another example when it is not working is when I am scaling application up/down - it does not reflect real amount of application pods.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 8 months
[JBoss JIRA] (JBIDE-22913) Server Adapter: Publish does not work
by Marián Labuda (JIRA)
[ https://issues.jboss.org/browse/JBIDE-22913?page=com.atlassian.jira.plugi... ]
Marián Labuda closed JBIDE-22913.
---------------------------------
Verified in DevStudio 10.1.0.AM3 build ID AM3-v20160812-0415-B5753.
> Server Adapter: Publish does not work
> -------------------------------------
>
> Key: JBIDE-22913
> URL: https://issues.jboss.org/browse/JBIDE-22913
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: openshift
> Affects Versions: 4.4.1.AM3
> Reporter: Marián Labuda
> Assignee: Nick Boldt
> Priority: Blocker
> Labels: openshift_v3, server_adapter_wizard
> Fix For: 4.4.1.AM3
>
>
> When I create a new OpenShift 3 server adapter with already running application pod, I get following error in error dialog and initial publish does not work. Autopublish does not work at all and also manual triggering of publishment throws same error.
> {code}
> Could not sync /home/mlabuda/workspaces/0804/.metadata/.plugins/org.jboss.ide.eclipse.as.core/projectname000@eap-app/deploy to all pods running the service eap-app
> OpenShiftBinaryCapability process exited: WARNING: rsync command not found in path. Please use your package manager to install it.
> Ignoring the following flags because they only apply to rsync: --exclude, --no-perms
> tar: ROOT.war/META-INF/MANIFEST.MF: Cannot open: Not a directory
> tar: ROOT.war/META-INF/maven/org.jboss.quickstarts.eap/jboss-kitchensink/pom.properties: Cannot open: Not a directory
> tar: ROOT.war/META-INF/maven/org.jboss.quickstarts.eap/jboss-kitchensink/pom.xml: Cannot open: Not a directory
> tar: ROOT.war/WEB-INF/beans.xml: Cannot open: Not a directory
> tar: ROOT.war/WEB-INF/classes/META-INF/persistence.xml: Cannot open: Not a directory
> tar: ROOT.war/WEB-INF/classes/import.sql: Cannot open: Not a directory
> tar: ROOT.war/WEB-INF/classes/org/jboss/as/quickstarts/kitchensink/controller/MemberController.class: Cannot open: Not a directory
> tar: ROOT.war/WEB-INF/classes/org/jboss/as/quickstarts/kitchensink/data/MemberListProducer.class: Cannot open: Not a directory
> tar: ROOT.war/WEB-INF/classes/org/jboss/as/quickstarts/kitchensink/data/MemberRepository.class: Cannot open: Not a directory
> tar: ROOT.war/WEB-INF/classes/org/jboss/as/quickstarts/kitchensink/model/Member.class: Cannot open: Not a directory
> tar: ROOT.war/WEB-INF/classes/org/jboss/as/quickstarts/kitchensink/rest/JaxRsActivator.class: Cannot open: Not a directory
> tar: ROOT.war/WEB-INF/classes/org/jboss/as/quickstarts/kitchensink/rest/MemberResourceRESTService.class: Cannot open: Not a directory
> tar: ROOT.war/WEB-INF/classes/org/jboss/as/quickstarts/kitchensink/service/MemberRegistration.class: Cannot open: Not a directory
> tar: ROOT.war/WEB-INF/classes/org/jboss/as/quickstarts/kitchensink/util/Resources.class: Cannot open: Not a directory
> tar: ROOT.war/WEB-INF/faces-config.xml: Cannot open: Not a directory
> tar: ROOT.war/WEB-INF/kitchensink-quickstart-ds.xml: Cannot open: Not a directory
> tar: ROOT.war/WEB-INF/templates/default.xhtml: Cannot open: Not a directory
> tar: ROOT.war/index.html: Cannot open: Not a directory
> tar: ROOT.war/index.xhtml: Cannot open: Not a directory
> tar: ROOT.war/resources/css/screen.css: Cannot open: Not a directory
> tar: ROOT.war/resources/gfx/asidebkg.png: Cannot open: Not a directory
> tar: ROOT.war/resources/gfx/banner.png: Cannot open: Not a directory
> tar: ROOT.war/resources/gfx/bkg-blkheader.png: Cannot open: Not a directory
> tar: ROOT.war/resources/gfx/headerbkg.png: Cannot open: Not a directory
> tar: ROOT.war/resources/gfx/rhjb_eap_logo.png: Cannot open: Not a directory
> tar: Exiting with failure status due to previous errors
> error: error extracting tar at destination directory: error executing remote command: Error executing command in container: Error executing in Docker Container: 2
> {code}
> I have installed rsync rsync-3.1.2-2.fc24.x86_64. I tried oc binary 1.2.0. and also 1.2.1. Issue describes not found rsync on PATH, although it is present there.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 8 months
[JBoss JIRA] (JBIDE-22992) OpenShift tools use wrong rest client bits
by Andre Dietisheim (JIRA)
[ https://issues.jboss.org/browse/JBIDE-22992?page=com.atlassian.jira.plugi... ]
Andre Dietisheim commented on JBIDE-22992:
------------------------------------------
[~jeffmaury] local client bundle was latest source containing latest embedded client jar.
> OpenShift tools use wrong rest client bits
> ------------------------------------------
>
> Key: JBIDE-22992
> URL: https://issues.jboss.org/browse/JBIDE-22992
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: build, openshift
> Affects Versions: 4.4.1.AM3
> Environment: eclipse.buildId=10.1.0.AM3-v20160810-0441-B5735
> java.version=1.8.0_101
> java.vendor=Oracle Corporation
> BootLoader constants: OS=win32, ARCH=x86_64, WS=win32, NL=en_US
> Framework arguments: -product com.jboss.devstudio.core.product
> Command-line arguments: -os win32 -ws win32 -arch x86_64 -product com.jboss.devstudio.core.product
> Reporter: Denis Golovin
> Assignee: Fred Bricon
> Priority: Blocker
> Fix For: 4.4.1.AM3
>
>
> An internal error occurred during: "Loading service-manager to configure additional frameworks that CDK depends on.".{code}java.lang.NoSuchMethodError: com.openshift.restclient.ClientBuilder.withMaxRequests(I)Lcom/openshift/restclient/ClientBuilder;
> at org.jboss.tools.openshift.core.connection.ConnectionFactory.create(ConnectionFactory.java:53)
> at org.jboss.tools.openshift.core.connection.ConnectionFactory.create(ConnectionFactory.java:1)
> at org.jboss.tools.openshift.cdk.server.core.internal.listeners.CDKOpenshiftUtility.createOpenshiftConnection(CDKOpenshiftUtility.java:77)
> at org.jboss.tools.openshift.cdk.server.core.internal.listeners.CDKOpenshiftUtility.createOpenshiftConnection(CDKOpenshiftUtility.java:55)
> at org.jboss.tools.openshift.cdk.server.core.internal.listeners.ConfigureDependentFrameworksListener.configureOpenshift(ConfigureDependentFrameworksListener.java:91)
> at org.jboss.tools.openshift.cdk.server.core.internal.listeners.ConfigureDependentFrameworksListener.configureFrameworks(ConfigureDependentFrameworksListener.java:56)
> at org.jboss.tools.openshift.cdk.server.core.internal.listeners.ConfigureDependentFrameworksListener$1.run(ConfigureDependentFrameworksListener.java:44)
> at org.eclipse.core.internal.jobs.Worker.run(Worker.java:55){code}
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 8 months