[JBoss JIRA] (JBIDE-26794) OpenShift: Remote debugging is very slow
by André Dietisheim (Jira)
[ https://issues.jboss.org/browse/JBIDE-26794?page=com.atlassian.jira.plugi... ]
André Dietisheim edited comment on JBIDE-26794 at 8/26/19 4:13 PM:
-------------------------------------------------------------------
[~jgammonred612] thanks a lot for reporting this. Definitely worth investigating.
I tried IntelliJ and also VSCode. VSCode behaves pretty much on par with Eclipse speedwise. IntelliJ on the other hand is noticeably quicker.
It is noticeable in all 3 how building the callstack is very slow. Eclipse/VSCode are quite unresponsive displaying the call stack and slow to accept inputs. IntelliJ stays very responsive, you can fluently step over while the call stack is still being built.
I definitely think that this is a platform issue and needs to be improved in the Eclipse/VSCode platform. IntelliJ has a noticeable advantage here. On the other hand, remote debugging - I think - isn't the dominant usecase.
Compare yourself:
* Eclipse
*
was (Author: adietish):
[~jgammonred612] thanks a lot for reporting this. Definitely worth investigating.
I tried IntelliJ and also VSCode. VSCode behaves pretty much on par with Eclipse speedwise. IntelliJ on the other hand is noticeably quicker.
It is noticeable in all 3 how building the callstack is very slow. Eclipse/VSCode are quite unresponsive displaying the call stack and slow to accept inputs. IntelliJ stays very responsive, you can fluently step over while the call stack is still being built.
I definitely think that this is a platform issue and needs to be improved in the Eclipse/VSCode platform. IntelliJ has a noticeable advantage here. On the other hand, remote debugging - I think - isn't the dominant usecase.
> OpenShift: Remote debugging is very slow
> ----------------------------------------
>
> Key: JBIDE-26794
> URL: https://issues.jboss.org/browse/JBIDE-26794
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: openshift
> Affects Versions: 4.11.0.Final
> Environment: Version: 12.11.0.GA
> Build id: GA-v20190329-0120-B4247
> Build date: 20190329-0120
> RHPDS
> Reporter: Josef Kopriva
> Assignee: André Dietisheim
> Priority: Critical
> Fix For: 4.13.x
>
>
> From Email on devtools-team from [~jgammonred612]:
> {code:java}
> Hi Folks:
> Using this version of Code Ready Studio
> Version: 12.11.0.GA
> Build id: GA-v20190329-0120-B4247
> Build date: 20190329-0120
> I recently ran an Openshift Starter Workshop lab and witnessed a clear
> issue with Code Ready Studio and INtelliJ
> Workshop Starter Lab
> (http://starter-guides-labs.b9ad.pro-us-east-1.openshiftapps.com/workshop/...)
> Lab 19 has a remote debugging setup. The remote debugger in Code Ready
> connected very very slowly and would not step over or step out making
> using it as a debugger virtually impossible.
> One of the lab participants had IntelliJ and it connected immediately
> and worked just fine.
> Clearly, something is broken in CRS. Maybe someone would want to test
> this out and fix?
> You can find this lab on RHPDS.
> Just FYI to the PM's.
> {code}
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
6 years, 7 months
[JBoss JIRA] (JBIDE-26794) OpenShift: Remote debugging is very slow
by André Dietisheim (Jira)
[ https://issues.jboss.org/browse/JBIDE-26794?page=com.atlassian.jira.plugi... ]
André Dietisheim edited comment on JBIDE-26794 at 8/26/19 4:04 PM:
-------------------------------------------------------------------
[~jgammonred612] thanks a lot for reporting this. Definitely worth investigating.
I tried IntelliJ and also VSCode. VSCode behaves pretty much on par with Eclipse speedwise. IntelliJ on the other hand is noticeably quicker.
It is noticeable in all 3 how building the callstack is very slow. Eclipse/VSCode are quite unresponsive displaying the call stack and slow to accept inputs. IntelliJ stays very responsive, you can fluently step over while the call stack is still being built.
I definitely think that this is a platform issue and needs to be improved in the Eclipse/VSCode platform. IntelliJ has a noticeable advantage here. On the other hand, remote debugging - I think - isn't the dominant usecase.
was (Author: adietish):
[~jgammonred612] thanks a lot for reporting this. Definitely worth investigating.
I tried IntelliJ and also VSCode. VSCode behaves pretty much on par with Eclipse speedwise. IntelliJ on the other hand is noticeably quicker.
It is noticeable in all 3 how building the callstack is very slow. Eclipse/VSCode are unresponsive displaying the call stack and wont accept inputs nor any other operation while the stack is being displayed. IntelliJ stays responsive, you can step over while the call stack is still being built.
I definitely think that this is a platform issue and needs to be improved in the Eclipse/VSCode platform. IntelliJ has a noticeable advantage here. On the other hand, remote debugging - I think - isn't the dominant usecase.
> OpenShift: Remote debugging is very slow
> ----------------------------------------
>
> Key: JBIDE-26794
> URL: https://issues.jboss.org/browse/JBIDE-26794
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: openshift
> Affects Versions: 4.11.0.Final
> Environment: Version: 12.11.0.GA
> Build id: GA-v20190329-0120-B4247
> Build date: 20190329-0120
> RHPDS
> Reporter: Josef Kopriva
> Assignee: André Dietisheim
> Priority: Critical
> Fix For: 4.13.x
>
>
> From Email on devtools-team from [~jgammonred612]:
> {code:java}
> Hi Folks:
> Using this version of Code Ready Studio
> Version: 12.11.0.GA
> Build id: GA-v20190329-0120-B4247
> Build date: 20190329-0120
> I recently ran an Openshift Starter Workshop lab and witnessed a clear
> issue with Code Ready Studio and INtelliJ
> Workshop Starter Lab
> (http://starter-guides-labs.b9ad.pro-us-east-1.openshiftapps.com/workshop/...)
> Lab 19 has a remote debugging setup. The remote debugger in Code Ready
> connected very very slowly and would not step over or step out making
> using it as a debugger virtually impossible.
> One of the lab participants had IntelliJ and it connected immediately
> and worked just fine.
> Clearly, something is broken in CRS. Maybe someone would want to test
> this out and fix?
> You can find this lab on RHPDS.
> Just FYI to the PM's.
> {code}
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
6 years, 7 months
[JBoss JIRA] (JBIDE-26794) OpenShift: Remote debugging is very slow
by André Dietisheim (Jira)
[ https://issues.jboss.org/browse/JBIDE-26794?page=com.atlassian.jira.plugi... ]
André Dietisheim edited comment on JBIDE-26794 at 8/26/19 3:51 PM:
-------------------------------------------------------------------
[~jgammonred612] thanks a lot for reporting this. Definitely worth investigating.
I tried IntelliJ and also VSCode. VSCode behaves pretty much on par with Eclipse speedwise. IntelliJ on the other hand is noticeably quicker.
It is noticeable in all 3 how building the callstack is very slow. Eclipse/VSCode are unresponsive displaying the call stack and wont accept inputs nor any other operation while the stack is being displayed. IntelliJ stays responsive, you can step over while the call stack is still being built.
I definitely think that this is a platform issue and needs to be improved in the Eclipse/VSCode platform. IntelliJ has a noticeable advantage here. On the other hand, remote debugging - I think - isn't the dominant usecase.
was (Author: adietish):
I tried IntelliJ and also VSCode. VSCode behaves pretty much on par with Eclipse speedwise. IntelliJ on the other hand is noticeably quicker.
It is noticeable in all 3 how building the callstack is very slow. Eclipse/VSCode are unresponsive displaying the call stack and wont accept inputs nor any other operation while the stack is being displayed. IntelliJ stays responsive, you can step over while the call stack is still being built.
I definitely think that this is a platform issue and needs to be improved in the Eclipse/VSCode platform. IntelliJ has a noticeable advantage here. On the other hand, remote debugging - I think - isn't the dominant usecase.
> OpenShift: Remote debugging is very slow
> ----------------------------------------
>
> Key: JBIDE-26794
> URL: https://issues.jboss.org/browse/JBIDE-26794
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: openshift
> Affects Versions: 4.11.0.Final
> Environment: Version: 12.11.0.GA
> Build id: GA-v20190329-0120-B4247
> Build date: 20190329-0120
> RHPDS
> Reporter: Josef Kopriva
> Assignee: André Dietisheim
> Priority: Critical
> Fix For: 4.13.x
>
>
> From Email on devtools-team from [~jgammonred612]:
> {code:java}
> Hi Folks:
> Using this version of Code Ready Studio
> Version: 12.11.0.GA
> Build id: GA-v20190329-0120-B4247
> Build date: 20190329-0120
> I recently ran an Openshift Starter Workshop lab and witnessed a clear
> issue with Code Ready Studio and INtelliJ
> Workshop Starter Lab
> (http://starter-guides-labs.b9ad.pro-us-east-1.openshiftapps.com/workshop/...)
> Lab 19 has a remote debugging setup. The remote debugger in Code Ready
> connected very very slowly and would not step over or step out making
> using it as a debugger virtually impossible.
> One of the lab participants had IntelliJ and it connected immediately
> and worked just fine.
> Clearly, something is broken in CRS. Maybe someone would want to test
> this out and fix?
> You can find this lab on RHPDS.
> Just FYI to the PM's.
> {code}
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
6 years, 7 months
[JBoss JIRA] (JBIDE-26794) OpenShift: Remote debugging is very slow
by André Dietisheim (Jira)
[ https://issues.jboss.org/browse/JBIDE-26794?page=com.atlassian.jira.plugi... ]
André Dietisheim edited comment on JBIDE-26794 at 8/26/19 3:51 PM:
-------------------------------------------------------------------
[~jgammonred612] thanks a lot for reporting this. Definitely worth investigating.
I tried IntelliJ and also VSCode. VSCode behaves pretty much on par with Eclipse speedwise. IntelliJ on the other hand is noticeably quicker.
It is noticeable in all 3 how building the callstack is very slow. Eclipse/VSCode are unresponsive displaying the call stack and wont accept inputs nor any other operation while the stack is being displayed. IntelliJ stays responsive, you can step over while the call stack is still being built.
I definitely think that this is a platform issue and needs to be improved in the Eclipse/VSCode platform. IntelliJ has a noticeable advantage here. On the other hand, remote debugging - I think - isn't the dominant usecase.
was (Author: adietish):
[~jgammonred612] thanks a lot for reporting this. Definitely worth investigating.
I tried IntelliJ and also VSCode. VSCode behaves pretty much on par with Eclipse speedwise. IntelliJ on the other hand is noticeably quicker.
It is noticeable in all 3 how building the callstack is very slow. Eclipse/VSCode are unresponsive displaying the call stack and wont accept inputs nor any other operation while the stack is being displayed. IntelliJ stays responsive, you can step over while the call stack is still being built.
I definitely think that this is a platform issue and needs to be improved in the Eclipse/VSCode platform. IntelliJ has a noticeable advantage here. On the other hand, remote debugging - I think - isn't the dominant usecase.
> OpenShift: Remote debugging is very slow
> ----------------------------------------
>
> Key: JBIDE-26794
> URL: https://issues.jboss.org/browse/JBIDE-26794
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: openshift
> Affects Versions: 4.11.0.Final
> Environment: Version: 12.11.0.GA
> Build id: GA-v20190329-0120-B4247
> Build date: 20190329-0120
> RHPDS
> Reporter: Josef Kopriva
> Assignee: André Dietisheim
> Priority: Critical
> Fix For: 4.13.x
>
>
> From Email on devtools-team from [~jgammonred612]:
> {code:java}
> Hi Folks:
> Using this version of Code Ready Studio
> Version: 12.11.0.GA
> Build id: GA-v20190329-0120-B4247
> Build date: 20190329-0120
> I recently ran an Openshift Starter Workshop lab and witnessed a clear
> issue with Code Ready Studio and INtelliJ
> Workshop Starter Lab
> (http://starter-guides-labs.b9ad.pro-us-east-1.openshiftapps.com/workshop/...)
> Lab 19 has a remote debugging setup. The remote debugger in Code Ready
> connected very very slowly and would not step over or step out making
> using it as a debugger virtually impossible.
> One of the lab participants had IntelliJ and it connected immediately
> and worked just fine.
> Clearly, something is broken in CRS. Maybe someone would want to test
> this out and fix?
> You can find this lab on RHPDS.
> Just FYI to the PM's.
> {code}
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
6 years, 7 months
[JBoss JIRA] (JBIDE-26794) OpenShift: Remote debugging is very slow
by André Dietisheim (Jira)
[ https://issues.jboss.org/browse/JBIDE-26794?page=com.atlassian.jira.plugi... ]
André Dietisheim edited comment on JBIDE-26794 at 8/26/19 3:50 PM:
-------------------------------------------------------------------
I tried IntelliJ and also VSCode. VSCode behaves pretty much on par with Eclipse speedwise. IntelliJ on the other hand is noticeably quicker.
It is noticeable in all 3 how building the callstack is very slow. Eclipse/VSCode are unresponsive displaying the call stack and wont accept inputs nor any other operation while the stack is being displayed. IntelliJ stays responsive, you can step over while the call stack is still being built.
I definitely think that this is a platform issue and needs to be improved in the Eclipse/VSCode platform. IntelliJ has a noticeable advantage here. On the other hand, remote debugging - I think - isn't the dominant usecase.
was (Author: adietish):
I tried IntelliJ and also VSCode. VSCode behaves pretty much on par to Eclipse speedwise. IntelliJ on the other hand is noticeably quicker. It is noticeable in all 3 how building the callstack is very slow. While Eclipse/VSCode feel singlethreaded and wont accept inputs nor any other operation while the stack is being displayed, IntelliJ seems to do it in a separate (background) thread, it stays responsive even while building the callstack.
I definitely think that this is a platform issue and needs to be improved in the Eclipse/VSCode platform. IntelliJ has a noticeable advantage here. On the other hand, remote debugging - I think - isn't the dominant usecase.
> OpenShift: Remote debugging is very slow
> ----------------------------------------
>
> Key: JBIDE-26794
> URL: https://issues.jboss.org/browse/JBIDE-26794
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: openshift
> Affects Versions: 4.11.0.Final
> Environment: Version: 12.11.0.GA
> Build id: GA-v20190329-0120-B4247
> Build date: 20190329-0120
> RHPDS
> Reporter: Josef Kopriva
> Assignee: André Dietisheim
> Priority: Critical
> Fix For: 4.13.x
>
>
> From Email on devtools-team from [~jgammonred612]:
> {code:java}
> Hi Folks:
> Using this version of Code Ready Studio
> Version: 12.11.0.GA
> Build id: GA-v20190329-0120-B4247
> Build date: 20190329-0120
> I recently ran an Openshift Starter Workshop lab and witnessed a clear
> issue with Code Ready Studio and INtelliJ
> Workshop Starter Lab
> (http://starter-guides-labs.b9ad.pro-us-east-1.openshiftapps.com/workshop/...)
> Lab 19 has a remote debugging setup. The remote debugger in Code Ready
> connected very very slowly and would not step over or step out making
> using it as a debugger virtually impossible.
> One of the lab participants had IntelliJ and it connected immediately
> and worked just fine.
> Clearly, something is broken in CRS. Maybe someone would want to test
> this out and fix?
> You can find this lab on RHPDS.
> Just FYI to the PM's.
> {code}
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
6 years, 7 months
[JBoss JIRA] (JBIDE-26794) OpenShift: Remote debugging is very slow
by André Dietisheim (Jira)
[ https://issues.jboss.org/browse/JBIDE-26794?page=com.atlassian.jira.plugi... ]
André Dietisheim commented on JBIDE-26794:
------------------------------------------
I tried IntelliJ and also VSCode. VSCode behaves pretty much on par to Eclipse speedwise. IntelliJ on the other hand is noticeably quicker. It is noticeable in all 3 how building the callstack is very slow. While Eclipse/VSCode feel singlethreaded and wont accept inputs nor any other operation while the stack is being displayed, IntelliJ seems to do it in a separate (background) thread, it stays responsive even while building the callstack.
I definitely think that this is a platform issue and needs to be improved in the Eclipse/VSCode platform. IntelliJ has a noticeable advantage here. On the other hand, remote debugging - I think - isn't the dominant usecase.
> OpenShift: Remote debugging is very slow
> ----------------------------------------
>
> Key: JBIDE-26794
> URL: https://issues.jboss.org/browse/JBIDE-26794
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: openshift
> Affects Versions: 4.11.0.Final
> Environment: Version: 12.11.0.GA
> Build id: GA-v20190329-0120-B4247
> Build date: 20190329-0120
> RHPDS
> Reporter: Josef Kopriva
> Assignee: André Dietisheim
> Priority: Critical
> Fix For: 4.13.x
>
>
> From Email on devtools-team from [~jgammonred612]:
> {code:java}
> Hi Folks:
> Using this version of Code Ready Studio
> Version: 12.11.0.GA
> Build id: GA-v20190329-0120-B4247
> Build date: 20190329-0120
> I recently ran an Openshift Starter Workshop lab and witnessed a clear
> issue with Code Ready Studio and INtelliJ
> Workshop Starter Lab
> (http://starter-guides-labs.b9ad.pro-us-east-1.openshiftapps.com/workshop/...)
> Lab 19 has a remote debugging setup. The remote debugger in Code Ready
> connected very very slowly and would not step over or step out making
> using it as a debugger virtually impossible.
> One of the lab participants had IntelliJ and it connected immediately
> and worked just fine.
> Clearly, something is broken in CRS. Maybe someone would want to test
> this out and fix?
> You can find this lab on RHPDS.
> Just FYI to the PM's.
> {code}
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
6 years, 7 months
[JBoss JIRA] (JBIDE-26794) OpenShift: Remote debugging is very slow
by André Dietisheim (Jira)
[ https://issues.jboss.org/browse/JBIDE-26794?page=com.atlassian.jira.plugi... ]
André Dietisheim commented on JBIDE-26794:
------------------------------------------
using the template that's shipped with the project works for me as long as I replace the s2-java docker image (which to my understanding doesn't support launching the jvm with the remote debugger agent turned on - what am I missing?) by the fabric8 one:
steps:
# ASSERT: have https://github.com/openshift-roadshow/nationalparks.git clone and imported into your workspace
# EXEC: modify the template at ose3/application-template.json, replace *jorgemoralespou/s2i-java* -> *fabric8/s2i-java*
{code:title=line 124}
"from": {
"kind": "DockerImage",
"name": "fabric8/s2i-java"
}
{code}
# EXEC: launch OpenShift application wizard, pick "Custom Template" > Browse Workspace & select ose3/application-template.json
# EXEC: do not import the source (since you already have it) & manually create a server adapter
# ASSERT: when the adapter is syncing, it'll report an error about BOOT-INF not existing in the pod. Ignore it.
# EXEC: Restart the adapter into debug
# EXEC: set a breakpoint at BackendController.get()
{code}
public Backend get() {
return new Backend("nationalparks","National Parks", new Coordinates("47.039304", "14.505178"), 4);
}
{code}
# EXEC: in "OpenShift Explorer": select "nationalparks" service, pick Show In > Web Browser
# ASSERT: Browser opens up with a 404
# EXEC: append */ws/info/* to the url
Result:
Eclipse debugger gets invoked, but indeed is very slow, almost unusable (was using employee.openshift.com)
> OpenShift: Remote debugging is very slow
> ----------------------------------------
>
> Key: JBIDE-26794
> URL: https://issues.jboss.org/browse/JBIDE-26794
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: openshift
> Affects Versions: 4.11.0.Final
> Environment: Version: 12.11.0.GA
> Build id: GA-v20190329-0120-B4247
> Build date: 20190329-0120
> RHPDS
> Reporter: Josef Kopriva
> Assignee: André Dietisheim
> Priority: Critical
> Fix For: 4.13.x
>
>
> From Email on devtools-team from [~jgammonred612]:
> {code:java}
> Hi Folks:
> Using this version of Code Ready Studio
> Version: 12.11.0.GA
> Build id: GA-v20190329-0120-B4247
> Build date: 20190329-0120
> I recently ran an Openshift Starter Workshop lab and witnessed a clear
> issue with Code Ready Studio and INtelliJ
> Workshop Starter Lab
> (http://starter-guides-labs.b9ad.pro-us-east-1.openshiftapps.com/workshop/...)
> Lab 19 has a remote debugging setup. The remote debugger in Code Ready
> connected very very slowly and would not step over or step out making
> using it as a debugger virtually impossible.
> One of the lab participants had IntelliJ and it connected immediately
> and worked just fine.
> Clearly, something is broken in CRS. Maybe someone would want to test
> this out and fix?
> You can find this lab on RHPDS.
> Just FYI to the PM's.
> {code}
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
6 years, 7 months
[JBoss JIRA] (JBIDE-26792) OpenShift ITests: Fix failing ServerAdapterFromResourceTest
by Josef Kopriva (Jira)
[ https://issues.jboss.org/browse/JBIDE-26792?page=com.atlassian.jira.plugi... ]
Josef Kopriva updated JBIDE-26792:
----------------------------------
Fix Version/s: 4.13.0.AM1
> OpenShift ITests: Fix failing ServerAdapterFromResourceTest
> -----------------------------------------------------------
>
> Key: JBIDE-26792
> URL: https://issues.jboss.org/browse/JBIDE-26792
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: integration-tests, openshift
> Affects Versions: 4.13.0.AM1
> Reporter: Josef Kopriva
> Assignee: Josef Kopriva
> Priority: Major
> Fix For: 4.13.0.AM1
>
>
> Test is failing on Jenkins:
> {code:java}
> org.eclipse.reddeer.common.exception.WaitTimeoutExpiredException:
> Timeout after: 120 s.: The following jobs are still running:
> Publishing to nodejs-example (Service) at OpenShift (127.0.0.1)...
> Stopping nodejs-example (Service) at OpenShift (127.0.0.1)
> Building workspace
> at org.jboss.tools.openshift.ui.bot.test.application.v3.adapter.ServerAdapterFromResourceTest.removeAdapterIfExists(ServerAdapterFromResourceTest.java:128)
> {code}
>
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
6 years, 7 months