[JBoss JIRA] (JBIDE-22957) 3rd party caused CoreException below ArquillianUIUtil.getActiveType
by Snjezana Peco (JIRA)
[ https://issues.jboss.org/browse/JBIDE-22957?page=com.atlassian.jira.plugi... ]
Snjezana Peco updated JBIDE-22957:
----------------------------------
Fix Version/s: 4.4.3.AM1
(was: 4.4.2.Final)
> 3rd party caused CoreException below ArquillianUIUtil.getActiveType
> -------------------------------------------------------------------
>
> Key: JBIDE-22957
> URL: https://issues.jboss.org/browse/JBIDE-22957
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: arquillian, upstream
> Affects Versions: 4.4.1.AM2
> Reporter: Automated Error Reporting Bot
> Assignee: Snjezana Peco
> Fix For: 4.4.3.AM1
>
>
> The following problem was reported via the automated error reporting:
> Message: GAE SDK /Users/villevenalainen/.m2/repository/com/google/appengine/appengine-api-1.0-sdk/1.9.34/appengine-api-1.0-sdk-1.9.34.jar failed validation
> {noformat}
> org.eclipse.core.runtime.CoreException: SDK location '/Users/villevenalainen/.m2/repository/com/google/appengine/appengine-api-1.0-sdk/1.9.34/appengine-api-1.0-sdk-1.9.34.jar' is not a directory
> at EXTERNAL.EXTERNAL(null:-1)
> at org.eclipse.jdt.internal.core.ReconcileWorkingCopyOperation$1.run(ReconcileWorkingCopyOperation.java:258)
> at org.eclipse.core.runtime.SafeRunner.run(SafeRunner.java:42)
> at org.eclipse.jdt.internal.core.ReconcileWorkingCopyOperation.notifyParticipants(ReconcileWorkingCopyOperation.java:245)
> at org.eclipse.jdt.internal.core.ReconcileWorkingCopyOperation.executeOperation(ReconcileWorkingCopyOperation.java:95)
> at org.eclipse.jdt.internal.core.JavaModelOperation.run(JavaModelOperation.java:729)
> at org.eclipse.jdt.internal.core.JavaModelOperation.runOperation(JavaModelOperation.java:789)
> at org.eclipse.jdt.internal.core.CompilationUnit.reconcile(CompilationUnit.java:1265)
> at org.eclipse.jdt.internal.core.CompilationUnit.reconcile(CompilationUnit.java:1224)
> at org.eclipse.jdt.internal.corext.util.JavaModelUtil.reconcile(JavaModelUtil.java:609)
> at org.eclipse.jdt.internal.ui.actions.SelectionConverter.getElementAtOffset(SelectionConverter.java:283)
> at org.eclipse.jdt.internal.ui.actions.SelectionConverter.getElementAtOffset(SelectionConverter.java:199)
> at org.eclipse.jdt.internal.ui.actions.SelectionConverter.getElementAtOffset(SelectionConverter.java:183)
> at org.jboss.tools.arquillian.ui.internal.utils.ArquillianUIUtil.getActiveType(ArquillianUIUtil.java:182)
> at org.jboss.tools.arquillian.ui.internal.commands.ArquillianPropertyTester.test(ArquillianPropertyTester.java:62)
> at org.eclipse.core.internal.expressions.Property.test(Property.java:58)
> at org.eclipse.core.internal.expressions.TestExpression.evaluate(TestExpression.java:100)
> at org.eclipse.core.internal.expressions.CompositeExpression.evaluateAnd(CompositeExpression.java:53)
> at org.eclipse.core.internal.expressions.AdaptExpression.evaluate(AdaptExpression.java:106)
> at org.eclipse.core.internal.expressions.CompositeExpression.evaluateOr(CompositeExpression.java:68)
> at org.eclipse.core.internal.expressions.OrExpression.evaluate(OrExpression.java:22)
> at org.eclipse.core.internal.expressions.CompositeExpression.evaluateAnd(CompositeExpression.java:53)
> at org.eclipse.core.internal.expressions.IterateExpression.evaluate(IterateExpression.java:199)
> at org.eclipse.core.internal.expressions.CompositeExpression.evaluateAnd(CompositeExpression.java:53)
> at org.eclipse.core.internal.expressions.WithExpression.evaluate(WithExpression.java:75)
> at org.eclipse.e4.ui.internal.workbench.ContributionsAnalyzer.isVisible(ContributionsAnalyzer.java:256)
> at org.eclipse.e4.ui.workbench.renderers.swt.ContributionRecord.computeVisibility(ContributionRecord.java:166)
> at org.eclipse.e4.ui.workbench.renderers.swt.ContributionRecord.updateVisibility(ContributionRecord.java:96)
> at org.eclipse.e4.ui.workbench.renderers.swt.MenuManagerRendererFilter.updateElementVisibility(MenuManagerRendererFilter.java:188)
> at org.eclipse.e4.ui.workbench.renderers.swt.MenuManagerRendererFilter.updateElementVisibility(MenuManagerRendererFilter.java:199)
> at org.eclipse.ui.internal.WorkbenchWindow$8.run(WorkbenchWindow.java:707)
> at org.eclipse.swt.widgets.RunnableLock.run(RunnableLock.java:35)
> at org.eclipse.swt.widgets.Synchronizer.runAsyncMessages(Synchronizer.java:135)
> at org.eclipse.swt.widgets.Display.runAsyncMessages(Display.java:4024)
> {noformat}
> Bundles:
> | org.eclipse.core.expressions | 3.5.0.v20150421-2214 | 3.5.0.v20150421-2214 |
> | org.eclipse.core.runtime | 3.11.1.v20150903-1804 | 3.11.1.v20150903-1804 |
> | org.eclipse.e4.ui.workbench | 1.3.1.v20160203-0951 | 1.3.1.v20160203-0951 |
> | org.eclipse.e4.ui.workbench.renderers.swt | 0.13.0.v20150901-1347 | 0.13.0.v20150901-1347 |
> | org.eclipse.jdt | 3.11.2.v20160212-1500 | 3.11.2.v20160212-1500 |
> | org.eclipse.jdt.core | 3.11.2.v_OTDT_r242_201601310642 | 3.11.2.v_OTDT_r242_201601310642 |
> | org.eclipse.jdt.ui | 3.11.2.v20151123-1510 | 3.11.2.v20151123-1510 |
> | org.eclipse.swt | 3.104.2.v20160212-1350 | 3.104.2.v20160212-1350 |
> | org.eclipse.ui | 3.107.0.v20150507-1945 | 3.107.0.v20150507-1945 |
> | org.jboss.tools.arquillian.ui | 1.2.1.Final-v20160331-0142-B69 | 1.2.1.Final-v20160331-0142-B69 |
> Operating Systems:
> | MacOSX | 10.11.5 | 10.11.5 |
> The above information is a snapshot of the collected data. Visit [this page|https://redhat.ctrlflow.com/reviewers/#!/problems/5791fa6fe4b07542de...] for the latest data.
> Thank you for your assistance.
> Your friendly error-reports-inbox.
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
9 years, 4 months
[JBoss JIRA] (JBIDE-22864) NullPointerException in ArquillianBuilder$3.visit
by Snjezana Peco (JIRA)
[ https://issues.jboss.org/browse/JBIDE-22864?page=com.atlassian.jira.plugi... ]
Snjezana Peco updated JBIDE-22864:
----------------------------------
Fix Version/s: 4.4.3.AM1
(was: 4.4.2.Final)
> NullPointerException in ArquillianBuilder$3.visit
> -------------------------------------------------
>
> Key: JBIDE-22864
> URL: https://issues.jboss.org/browse/JBIDE-22864
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: arquillian
> Affects Versions: 4.4.1.AM1
> Reporter: Automated Error Reporting Bot
> Assignee: Snjezana Peco
> Fix For: 4.4.3.AM1
>
>
> The following problem was reported via the automated error reporting:
> Message: HIDDEN
> {noformat}
> java.lang.NullPointerException: null
> at org.jboss.tools.arquillian.core.internal.builder.ArquillianBuilder$3.visit(ArquillianBuilder.java:731)
> at org.eclipse.jdt.core.dom.MethodInvocation.accept0(MethodInvocation.java:231)
> at org.eclipse.jdt.core.dom.ASTNode.accept(ASTNode.java:2711)
> at org.eclipse.jdt.core.dom.ASTNode.acceptChild(ASTNode.java:2759)
> at org.eclipse.jdt.core.dom.ReturnStatement.accept0(ReturnStatement.java:137)
> at org.eclipse.jdt.core.dom.ASTNode.accept(ASTNode.java:2711)
> at org.eclipse.jdt.core.dom.ASTNode.acceptChildren(ASTNode.java:2782)
> at org.eclipse.jdt.core.dom.Block.accept0(Block.java:137)
> at org.eclipse.jdt.core.dom.ASTNode.accept(ASTNode.java:2711)
> at org.eclipse.jdt.core.dom.ASTNode.acceptChild(ASTNode.java:2759)
> at org.eclipse.jdt.core.dom.MethodDeclaration.accept0(MethodDeclaration.java:635)
> at org.eclipse.jdt.core.dom.ASTNode.accept(ASTNode.java:2711)
> at org.jboss.tools.arquillian.core.internal.builder.ArquillianBuilder.validateArchiveFileLocation(ArquillianBuilder.java:653)
> at org.jboss.tools.arquillian.core.internal.builder.ArquillianBuilder.build(ArquillianBuilder.java:359)
> at org.jboss.tools.arquillian.core.internal.builder.ArquillianBuilder.buildDelta(ArquillianBuilder.java:222)
> at org.jboss.tools.arquillian.core.internal.builder.ArquillianBuilder.build(ArquillianBuilder.java:112)
> at org.eclipse.core.internal.events.BuildManager$2.run(BuildManager.java:735)
> at org.eclipse.core.runtime.SafeRunner.run(SafeRunner.java:42)
> at org.eclipse.core.internal.events.BuildManager.basicBuild(BuildManager.java:206)
> at org.eclipse.core.internal.events.BuildManager.basicBuild(BuildManager.java:246)
> at org.eclipse.core.internal.events.BuildManager$1.run(BuildManager.java:301)
> at org.eclipse.core.runtime.SafeRunner.run(SafeRunner.java:42)
> at org.eclipse.core.internal.events.BuildManager.basicBuild(BuildManager.java:304)
> at org.eclipse.core.internal.events.BuildManager.basicBuildLoop(BuildManager.java:360)
> at org.eclipse.core.internal.events.BuildManager.build(BuildManager.java:383)
> at org.eclipse.core.internal.events.AutoBuildJob.doBuild(AutoBuildJob.java:144)
> at org.eclipse.core.internal.events.AutoBuildJob.run(AutoBuildJob.java:235)
> at org.eclipse.core.internal.jobs.Worker.run(Worker.java:55)
> {noformat}
> Bundles:
> | org.eclipse.core.jobs | 3.8.0.v20160509-0411 | 3.8.0.v20160509-0411 |
> | org.eclipse.core.runtime | 3.12.0.v20160606-1342 | 3.12.0.v20160606-1342 |
> | org.eclipse.jdt.core | 3.12.0.v20160516-2131 | 3.12.0.v20160516-2131 |
> | org.jboss.tools.arquillian.core | 1.2.100.Final-v20160610-0313-B2 | 1.2.100.Final-v20160610-0313-B2 |
> Operating Systems:
> | MacOSX | 10.11.5 | 10.11.5 |
> The above information is a snapshot of the collected data. Visit [this page|https://redhat.ctrlflow.com/reviewers/#!/problems/5786f2afe4b07f3dc2...] for the latest data.
> Thank you for your assistance.
> Your friendly error-reports-inbox.
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
9 years, 4 months
[JBoss JIRA] (JBIDE-23003) NullPointerException below DependencyCache.getDependentTypes (thrown in AbstractCollection.addAll)
by Snjezana Peco (JIRA)
[ https://issues.jboss.org/browse/JBIDE-23003?page=com.atlassian.jira.plugi... ]
Snjezana Peco updated JBIDE-23003:
----------------------------------
Fix Version/s: 4.4.3.AM1
(was: 4.4.2.Final)
> NullPointerException below DependencyCache.getDependentTypes (thrown in AbstractCollection.addAll)
> --------------------------------------------------------------------------------------------------
>
> Key: JBIDE-23003
> URL: https://issues.jboss.org/browse/JBIDE-23003
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: arquillian
> Affects Versions: 4.4.0.Final
> Reporter: Automated Error Reporting Bot
> Assignee: Snjezana Peco
> Fix For: 4.4.3.AM1
>
>
> The following problem was reported via the automated error reporting:
> Message: Problems occurred when invoking code from plug-in: "org.eclipse.core.resources".
> {noformat}
> java.lang.NullPointerException: null
> at java.util.AbstractCollection.addAll(AbstractCollection.java:343)
> at org.jboss.tools.arquillian.core.internal.dependencies.DependencyCache.getDependentTypes(DependencyCache.java:101)
> at org.jboss.tools.arquillian.core.internal.builder.ArquillianBuilder.build(ArquillianBuilder.java:373)
> at org.jboss.tools.arquillian.core.internal.builder.ArquillianBuilder.buildDelta(ArquillianBuilder.java:222)
> at org.jboss.tools.arquillian.core.internal.builder.ArquillianBuilder.build(ArquillianBuilder.java:112)
> at org.eclipse.core.internal.events.BuildManager$2.run(BuildManager.java:734)
> at org.eclipse.core.runtime.SafeRunner.run(SafeRunner.java:42)
> at org.eclipse.core.internal.events.BuildManager.basicBuild(BuildManager.java:205)
> at org.eclipse.core.internal.events.BuildManager.basicBuild(BuildManager.java:245)
> at org.eclipse.core.internal.events.BuildManager$1.run(BuildManager.java:300)
> at org.eclipse.core.runtime.SafeRunner.run(SafeRunner.java:42)
> at org.eclipse.core.internal.events.BuildManager.basicBuild(BuildManager.java:303)
> at org.eclipse.core.internal.events.BuildManager.basicBuildLoop(BuildManager.java:359)
> at org.eclipse.core.internal.events.BuildManager.build(BuildManager.java:382)
> at org.eclipse.core.internal.events.AutoBuildJob.doBuild(AutoBuildJob.java:144)
> at org.eclipse.core.internal.events.AutoBuildJob.run(AutoBuildJob.java:235)
> at org.eclipse.core.internal.jobs.Worker.run(Worker.java:55)
> {noformat}
> Bundles:
> | org.eclipse.core.jobs | 3.7.0.v20150330-2103 | 3.7.0.v20150330-2103 |
> | org.eclipse.core.runtime | 3.11.1.v20150903-1804 | 3.11.1.v20150903-1804 |
> | org.jboss.tools.arquillian.core | 1.2.1.Final-v20160331-0142-B69 | 1.2.1.Final-v20160331-0142-B69 |
> Operating Systems:
> | Windows | 6.1.0 | 6.1.0 |
> The above information is a snapshot of the collected data. Visit [this page|https://redhat.ctrlflow.com/reviewers/#!/problems/57aab86ee4b0f4d912...] for the latest data.
> Thank you for your assistance.
> Your friendly error-reports-inbox.
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
9 years, 4 months
[JBoss JIRA] (JBIDE-22958) 3rd party caused NullPointerException below ArquillianUIUtil.addContainerProperties
by Snjezana Peco (JIRA)
[ https://issues.jboss.org/browse/JBIDE-22958?page=com.atlassian.jira.plugi... ]
Snjezana Peco updated JBIDE-22958:
----------------------------------
Fix Version/s: 4.4.3.AM1
(was: 4.4.2.Final)
> 3rd party caused NullPointerException below ArquillianUIUtil.addContainerProperties
> -----------------------------------------------------------------------------------
>
> Key: JBIDE-22958
> URL: https://issues.jboss.org/browse/JBIDE-22958
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: arquillian
> Affects Versions: 4.4.0.Final
> Reporter: Automated Error Reporting Bot
> Assignee: Snjezana Peco
> Fix For: 4.4.3.AM1
>
>
> The following problem was reported via the automated error reporting:
> Message:
> {noformat}
> java.lang.NullPointerException: null
> at EXTERNAL.EXTERNAL(null:-1)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(NativeMethodAccessorImpl.java:-2)
> at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
> at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> at java.lang.reflect.Method.invoke(Method.java:498)
> at org.jboss.tools.arquillian.ui.internal.utils.ArquillianUIUtil.addContainerProperties(ArquillianUIUtil.java:581)
> at org.jboss.tools.arquillian.ui.internal.utils.ArquillianUIUtil.getArquillianProperties(ArquillianUIUtil.java:507)
> at org.jboss.tools.arquillian.ui.internal.launcher.ArquillianTab.initializeFrom(ArquillianTab.java:644)
> at org.eclipse.debug.ui.AbstractLaunchConfigurationTab.activated(AbstractLaunchConfigurationTab.java:411)
> at org.eclipse.debug.internal.ui.launchConfigurations.LaunchConfigurationTabGroupViewer.handleTabSelected(LaunchConfigurationTabGroupViewer.java:1365)
> at org.eclipse.debug.internal.ui.launchConfigurations.LaunchConfigurationTabGroupViewer$6.widgetSelected(LaunchConfigurationTabGroupViewer.java:377)
> at org.eclipse.swt.widgets.TypedListener.handleEvent(TypedListener.java:248)
> at org.eclipse.swt.widgets.EventTable.sendEvent(EventTable.java:84)
> {noformat}
> Bundles:
> | org.eclipse.core.runtime | 3.11.1.v20150903-1804 | 3.11.1.v20150903-1804 |
> | org.eclipse.debug.ui | 3.11.101.v20160203-1230 | 3.11.101.v20160203-1230 |
> | org.eclipse.jface | 3.11.1.v20160128-1644 | 3.11.1.v20160128-1644 |
> | org.eclipse.swt | 3.104.2.v20160212-1350 | 3.104.2.v20160212-1350 |
> | org.eclipse.ui | 3.107.0.v20150507-1945 | 3.107.0.v20150507-1945 |
> | org.jboss.tools.arquillian.ui | 1.2.1.Final-v20160331-0142-B69 | 1.2.1.Final-v20160331-0142-B69 |
> Operating Systems:
> | Windows | 6.3.0 | 6.3.0 |
> The above information is a snapshot of the collected data. Visit [this page|https://redhat.ctrlflow.com/reviewers/#!/problems/57a34e3ce4b084ea94...] for the latest data.
> Thank you for your assistance.
> Your friendly error-reports-inbox.
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
9 years, 4 months
[JBoss JIRA] (JBIDE-23516) Server Adapter: DC of debugged java application use nodejs debugging env var
by Marián Labuda (JIRA)
[ https://issues.jboss.org/browse/JBIDE-23516?page=com.atlassian.jira.plugi... ]
Marián Labuda commented on JBIDE-23516:
---------------------------------------
Ok, in that case consider this one as rejected. I did not recall having DEV_MODE env var there earlier, that was the reason I created this JIRA. But as it looks like, we are moving to a common concept of having dev mode var across OS images.
> Server Adapter: DC of debugged java application use nodejs debugging env var
> ----------------------------------------------------------------------------
>
> Key: JBIDE-23516
> URL: https://issues.jboss.org/browse/JBIDE-23516
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: openshift
> Affects Versions: 4.4.2.Final
> Reporter: Marián Labuda
> Labels: debugging, openshift_v3, server_adapter
>
> When debugging an EAP application on OpenShift, deployment config is modified. In nodejs debugging there is added an environment variable DEV_MODE. For java debugging it is not necessary but I found it in deployment config. I compared deployment config before starting debugging and after and it was added by tooling.
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
9 years, 4 months
[JBoss JIRA] (JBIDE-23516) Server Adapter: DC of debugged java application use nodejs debugging env var
by Marián Labuda (JIRA)
[ https://issues.jboss.org/browse/JBIDE-23516?page=com.atlassian.jira.plugi... ]
Marián Labuda edited comment on JBIDE-23516 at 11/24/16 7:18 AM:
-----------------------------------------------------------------
Ok, in that case consider this one as rejected. I did not recall having DEV_MODE env var there earlier, that was the reason I created this JIRA. But as it looks like, we are moving to a concept of having dev mode var across OS images.
was (Author: mlabuda):
Ok, in that case consider this one as rejected. I did not recall having DEV_MODE env var there earlier, that was the reason I created this JIRA. But as it looks like, we are moving to a common concept of having dev mode var across OS images.
> Server Adapter: DC of debugged java application use nodejs debugging env var
> ----------------------------------------------------------------------------
>
> Key: JBIDE-23516
> URL: https://issues.jboss.org/browse/JBIDE-23516
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: openshift
> Affects Versions: 4.4.2.Final
> Reporter: Marián Labuda
> Labels: debugging, openshift_v3, server_adapter
>
> When debugging an EAP application on OpenShift, deployment config is modified. In nodejs debugging there is added an environment variable DEV_MODE. For java debugging it is not necessary but I found it in deployment config. I compared deployment config before starting debugging and after and it was added by tooling.
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
9 years, 4 months
[JBoss JIRA] (JBIDE-23422) Server Adapter: Node.js debug session is terminated after ~1 minute and browser shows 502 error
by Jeff MAURY (JIRA)
[ https://issues.jboss.org/browse/JBIDE-23422?page=com.atlassian.jira.plugi... ]
Jeff MAURY commented on JBIDE-23422:
------------------------------------
This is not doable as of now. We can launch a browser only from a service. So we are forced now to use the path that goes to the router.
A solution would be to add Open with Browser command that would first create a Port forwarding and then open a browser to that port.
> Server Adapter: Node.js debug session is terminated after ~1 minute and browser shows 502 error
> -----------------------------------------------------------------------------------------------
>
> Key: JBIDE-23422
> URL: https://issues.jboss.org/browse/JBIDE-23422
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: javascript, openshift
> Affects Versions: 4.4.2.AM2
> Environment: windows 10
> Fedora 24
> Reporter: Ilya Buziuk
> Assignee: Jeff MAURY
> Priority: Critical
> Labels: nodejs, openshift_v3, server_adapter
> Fix For: 4.4.3.AM1
>
>
> We've found, that when one is debugging (the code is stopeed at breakpoint, stepping through code, inspecting variables, ...) longer than ~1 minute, browser displays error code 502 and the debug session gets terminated. This makes this feature not very useful, because all debugging must be quicker than that timeout.
> The behavior is captured in this screencast: https://youtu.be/BJf7wcPqNmM (note how at the time 0:42 the page is finally loaded (502 error) and the debug session is terminated (in debug view)).
> We were able to reproduce this issue on F24 and Win10 (using CDK and console.engint.openshift.com)
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
9 years, 4 months
[JBoss JIRA] (JBIDE-23422) Server Adapter: Node.js debug session is terminated after ~1 minute and browser shows 502 error
by Andre Dietisheim (JIRA)
[ https://issues.jboss.org/browse/JBIDE-23422?page=com.atlassian.jira.plugi... ]
Andre Dietisheim updated JBIDE-23422:
-------------------------------------
Fix Version/s: 4.4.3.AM1
(was: 4.4.2.Final)
> Server Adapter: Node.js debug session is terminated after ~1 minute and browser shows 502 error
> -----------------------------------------------------------------------------------------------
>
> Key: JBIDE-23422
> URL: https://issues.jboss.org/browse/JBIDE-23422
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: javascript, openshift
> Affects Versions: 4.4.2.AM2
> Environment: windows 10
> Fedora 24
> Reporter: Ilya Buziuk
> Assignee: Jeff MAURY
> Priority: Critical
> Labels: nodejs, openshift_v3, server_adapter
> Fix For: 4.4.3.AM1
>
>
> We've found, that when one is debugging (the code is stopeed at breakpoint, stepping through code, inspecting variables, ...) longer than ~1 minute, browser displays error code 502 and the debug session gets terminated. This makes this feature not very useful, because all debugging must be quicker than that timeout.
> The behavior is captured in this screencast: https://youtu.be/BJf7wcPqNmM (note how at the time 0:42 the page is finally loaded (502 error) and the debug session is terminated (in debug view)).
> We were able to reproduce this issue on F24 and Win10 (using CDK and console.engint.openshift.com)
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
9 years, 4 months