[JBoss JIRA] (JBIDE-23165) application wizard: IllegalArgumentException in New OpenShift Application Wizard
by Andre Dietisheim (JIRA)
[ https://issues.jboss.org/browse/JBIDE-23165?page=com.atlassian.jira.plugi... ]
Andre Dietisheim updated JBIDE-23165:
-------------------------------------
Git Pull Request: https://github.com/jbosstools/jbosstools-openshift/pull/1328, https://github.com/jbosstools/jbosstools-openshift/pull/1334 (was: https://github.com/jbosstools/jbosstools-openshift/pull/1328)
> application wizard: IllegalArgumentException in New OpenShift Application Wizard
> --------------------------------------------------------------------------------
>
> Key: JBIDE-23165
> URL: https://issues.jboss.org/browse/JBIDE-23165
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: openshift
> Affects Versions: 4.4.1.Final
> Environment: Windows 10 Home
> OpenJDK 1.8
> Reporter: Denis Golovin
> Assignee: Dmitrii Bocharov
> Labels: application_wizard, openshift_v3
> Fix For: 4.4.2.AM2
>
> Attachments: error-verifying-user-credentials.png, oc3iare.gif
>
>
> {code}java.lang.IllegalArgumentException:
> at org.eclipse.core.runtime.Assert.isLegal(Assert.java:63)
> at org.eclipse.core.runtime.Assert.isLegal(Assert.java:47)
> at org.jboss.tools.openshift.internal.ui.wizard.connection.AdvancedConnectionEditor$ConnectionAdvancedPropertiesProvider.update(AdvancedConnectionEditor.java:191)
> at org.jboss.tools.openshift.internal.common.ui.connection.ConnectionWizardPage.onPageWillGetDeactivated(ConnectionWizardPage.java:370)
> 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.backPressed(WizardDialog.java:404)
> at org.eclipse.jface.wizard.WizardDialog.buttonPressed(WizardDialog.java:415)
> 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:4410)
> at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1079)
> at org.eclipse.swt.widgets.Display.runDeferredEvents(Display.java:4228)
> at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:3816)
> at org.eclipse.jface.window.Window.runEventLoop(Window.java:818)
> at org.eclipse.jface.window.Window.open(Window.java:794)
> at org.eclipse.ui.internal.handlers.WizardHandler$New.executeHandler(WizardHandler.java:269)
> at org.eclipse.ui.internal.handlers.WizardHandler.execute(WizardHandler.java:290)
> 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(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.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:488)
> at org.eclipse.e4.core.commands.internal.HandlerServiceImpl.executeHandler(HandlerServiceImpl.java:210)
> at org.eclipse.ui.internal.handlers.LegacyHandlerService.executeCommand(LegacyHandlerService.java:353)
> at org.eclipse.ui.internal.actions.CommandAction.runWithEvent(CommandAction.java:155)
> at org.eclipse.jface.action.ActionContributionItem.handleWidgetSelection(ActionContributionItem.java:565)
> at org.eclipse.jface.action.ActionContributionItem.lambda$4(ActionContributionItem.java:397)
> 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.Display.runDeferredEvents(Display.java:4228)
> at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:3816)
> 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 message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 6 months
[JBoss JIRA] (ERT-177) Selection and dependent functionality works wrong when a file is modified in JS Editor [EBZ#492998]
by Ilya Buziuk (JIRA)
[ https://issues.jboss.org/browse/ERT-177?page=com.atlassian.jira.plugin.sy... ]
Ilya Buziuk updated ERT-177:
----------------------------
Fix Version/s: Neon.2 (4.6)
(was: Neon (4.6) RC3)
> Selection and dependent functionality works wrong when a file is modified in JS Editor [EBZ#492998]
> ---------------------------------------------------------------------------------------------------
>
> Key: ERT-177
> URL: https://issues.jboss.org/browse/ERT-177
> Project: Eclipse Release Train
> Issue Type: Task
> Components: JSDT
> Reporter: Friendly Jira Robot
> Assignee: Victor Rubezhny
> Labels: 3.8_RC1, General, bzira
> Fix For: Neon.2 (4.6)
>
>
> Created attachment 261462
> Selection related errors
> See the screenshot attached for illustration.
> Steps for reproduce:
> - Create a javascript file with a function and a call to that function.
> - Try to invoke content assist: FAIL: no new function appears in CA proposals
> - Save, close and open the file again.
> - Try to invoke content assist: Now the new function appears in CA proposals
> - Put some text (like just new lines or some statements between the function declaration and its call and select the function name in the declaration
> - FAIL: See wrong text regions highlighted.
> - Try to rename the function (with inline rename): FAIL: See the wrong places for the inline editing are highlighted.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 6 months
[JBoss JIRA] (ERT-348) mouse hover over member variable does not show it value [EBZ#497965]
by Ilya Buziuk (JIRA)
[ https://issues.jboss.org/browse/ERT-348?page=com.atlassian.jira.plugin.sy... ]
Ilya Buziuk updated ERT-348:
----------------------------
Fix Version/s: Neon.2 (4.6)
> mouse hover over member variable does not show it value [EBZ#497965]
> --------------------------------------------------------------------
>
> Key: ERT-348
> URL: https://issues.jboss.org/browse/ERT-348
> Project: Eclipse Release Train
> Issue Type: Task
> Components: JSDT
> Reporter: Friendly Jira Robot
> Labels: Debug, bzira
> Fix For: Neon.2 (4.6)
>
>
> While debugging, if I hover with my mouse over “myVar” part of the expression “myVar.myProp.mySubProp.abc” in my JS editor, I see a tooltip with its current value. But if I hover over the last segment “abc” of the same expression nothing happens. If I want to see its value, I have to move the mouse to “myVar” and when the tooltip opens up I have to click to expand, scroll to “myProp”, click to expand, scroll to “mySubProp”, expand, etc. until I see “abc”. Would be a real time saver when I hover over “abc” to see its value.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 6 months
[JBoss JIRA] (ERT-348) mouse hover over member variable does not show it value [EBZ#497965]
by Ilya Buziuk (JIRA)
[ https://issues.jboss.org/browse/ERT-348?page=com.atlassian.jira.plugin.sy... ]
Ilya Buziuk reassigned ERT-348:
-------------------------------
Assignee: Ilya Buziuk
> mouse hover over member variable does not show it value [EBZ#497965]
> --------------------------------------------------------------------
>
> Key: ERT-348
> URL: https://issues.jboss.org/browse/ERT-348
> Project: Eclipse Release Train
> Issue Type: Task
> Components: JSDT
> Reporter: Friendly Jira Robot
> Assignee: Ilya Buziuk
> Labels: Debug, bzira
> Fix For: Neon.2 (4.6)
>
>
> While debugging, if I hover with my mouse over “myVar” part of the expression “myVar.myProp.mySubProp.abc” in my JS editor, I see a tooltip with its current value. But if I hover over the last segment “abc” of the same expression nothing happens. If I want to see its value, I have to move the mouse to “myVar” and when the tooltip opens up I have to click to expand, scroll to “myProp”, click to expand, scroll to “mySubProp”, expand, etc. until I see “abc”. Would be a real time saver when I hover over “abc” to see its value.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 6 months
[JBoss JIRA] (ERT-346) If I add a breakpoint to a project called "node_modules" the program is not suspended [EBZ#497703]
by Ilya Buziuk (JIRA)
[ https://issues.jboss.org/browse/ERT-346?page=com.atlassian.jira.plugin.sy... ]
Ilya Buziuk updated ERT-346:
----------------------------
Fix Version/s: Neon.2 (4.6)
> If I add a breakpoint to a project called "node_modules" the program is not suspended [EBZ#497703]
> --------------------------------------------------------------------------------------------------
>
> Key: ERT-346
> URL: https://issues.jboss.org/browse/ERT-346
> Project: Eclipse Release Train
> Issue Type: Task
> Components: JSDT
> Reporter: Friendly Jira Robot
> Assignee: Ilya Buziuk
> Labels: Debug, bzira
> Fix For: Neon.2 (4.6)
>
>
> We use feature in node that we can put out modules in a “node_modules” in a parent folder and it will be properly found: https://nodejs.org/api/modules.html#modules_loading_from_node_modules_fol...
> Node is working properly but if I add a breakpoint in a source file inside “node_modules” the breakpoint does not get hit.
> To reproduce the issue:
> 1. Create a JavaScript project “test”.
> 2. Add a file “test.js” to the project with content:
> var m1 = require("m1");
> console.log("m1.myFunc = " + m1.myFunc(3));
> 3. Create a JavaScript project called “node_modules”.
> 4. Add a folder “m1” to the project “node_modules”.
> 5. Add a file “index.js” to the folder “m1” with content:
> module.exports.myFunc = function( i) {
> return i*i;
> }
> 6. Debug “test.js” as Node – it works. Node is finding property “index.js”. 7. Add a breakpoint to “index.js”.
> 8. Debug “test.js” as Node – it runs, but the breakpoint does not suspend the target.
> Is there workaround for this issues?
> Most of our projects are relying on the “node_modules” being found in the parent folder. That is making most of our code hard to debug.
> I tested this on Ubuntu 14.04.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 6 months
[JBoss JIRA] (ERT-379) Exceptions while expanding Variables view [EBZ#499600]
by Ilya Buziuk (JIRA)
[ https://issues.jboss.org/browse/ERT-379?page=com.atlassian.jira.plugin.sy... ]
Ilya Buziuk updated ERT-379:
----------------------------
Fix Version/s: Neon.2 (4.6)
(was: Neon.1 (4.6))
> 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
> Assignee: Ilya Buziuk
> Labels: 3.8.2, Debug, bzira
> Fix For: Neon.2 (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, 6 months
[JBoss JIRA] (ERT-379) Exceptions while expanding Variables view [EBZ#499600]
by Ilya Buziuk (JIRA)
[ https://issues.jboss.org/browse/ERT-379?page=com.atlassian.jira.plugin.sy... ]
Ilya Buziuk updated ERT-379:
----------------------------
Labels: 3.8.2 Debug bzira (was: 3.8.1 Debug bzira)
> 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
> Assignee: Ilya Buziuk
> Labels: 3.8.2, Debug, bzira
> 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, 6 months