July 2018 - jbosstools-issues - Jboss List Archives

[JBoss JIRA] (JBIDE-26204) Pod Log, Port Forwarding: when using bogus oc, log console shows up empty & port forwarding isn't functioning

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-26204?page=com.atlassian.jira.plugi... ] Andre Dietisheim updated JBIDE-26204: ------------------------------------- Comment: was deleted (was: This only happens after the PR for JBIDE-25700 is applied) > Pod Log, Port Forwarding: when using bogus oc, log console shows up empty & port forwarding isn't functioning > ------------------------------------------------------------------------------------------------------------- > > Key: JBIDE-26204 > URL: https://issues.jboss.org/browse/JBIDE-26204 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.6.0.Final > Reporter: Andre Dietisheim > Assignee: Andre Dietisheim > Fix For: 4.9.0.AM1 > > Attachments: pod-log-console-empty.png, port-forwarding-stopped.png > > > * Setup: > *# ASSERT: use the code that in the [PR|https://github.com/jbosstools/jbosstools-openshift/pull/1772] for JBIDE-25700 > *# ASSERT: make sure you have an app with a pod running in OpenShift > *# EXEC: open OpenShift preferences and point it to an oc that is a bogus executable file (that you created ex. by doing "touch oc && chmod +x oc") > * Port Log: > *# EXEC: in OpenShift Explorer: select the pod and pick "Pod Log..." > *# Result: > The "Console" view shows up but nothing happens, there's no output. > !pod-log-console-empty.png! > * Port Forwarding: > *# EXEC: in OpenShift Explorer: select the pod and pick "Port Forwarding..." > *# ASSERT: Port Forwarding wizard shows up listing the forwardable ports, the "Status" column shows them "Stopped" > *# EXEC: hit "Start All" button > *# Result: > Port forwarding is not started, the "Status" column for the ports stays "Stopped" > !port-forwarding-stopped.png! -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 8 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-26086) SSP server does not send error codes for bad requests

by Rob Stryker (JIRA)

[ https://issues.jboss.org/browse/JBIDE-26086?page=com.atlassian.jira.plugi... ] Rob Stryker commented on JBIDE-26086: ------------------------------------- I've opened https://github.com/eclipse/lsp4j/issues/210 Let's see if it goes anywhere. > SSP server does not send error codes for bad requests > ----------------------------------------------------- > > Key: JBIDE-26086 > URL: https://issues.jboss.org/browse/JBIDE-26086 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: stack-server-protocol > Affects Versions: 4.6.0.AM3 > Reporter: Jan Richter > Assignee: Rob Stryker > > Sending a request the server does not like produces no response, it is simply logged on the server side and the client is not notified of what happened. Something like a code 400 would be appreciated. > For example, initiating a connection with no content-length header simply logs the following on the server side, but the client is stuck waiting. > {noformat}java.lang.IllegalStateException: Missing header Content-Length in input "GET / HTTP/1.1 > Sec-WebSocket-Version: 13 > Sec-WebSocket-Key: 4vrbTo0+BlSk5wK7si6SWQ== > Connection: Upgrade > Upgrade: websocket > Sec-WebSocket-Extensions: permessage-deflate; client_max_window_bits > Host: localhost:27511 > " > at org.eclipse.lsp4j.jsonrpc.json.StreamMessageProducer.listen(StreamMessageProducer.java:89) > at org.eclipse.lsp4j.jsonrpc.json.ConcurrentMessageProcessor.run(ConcurrentMessageProcessor.java:95) > at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511) > at java.util.concurrent.FutureTask.run(FutureTask.java:266) > at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149) > at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624) > at java.lang.Thread.run(Thread.java:748){noformat} > This is most likely a 'feature' of lsp4j, thoughts? -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 8 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-26204) Pod Log, Port Forwarding: when using bogus oc, log console shows up empty & port forwarding isn't functioning

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-26204?page=com.atlassian.jira.plugi... ] Andre Dietisheim updated JBIDE-26204: ------------------------------------- Description: * Setup: *# ASSERT: use the code that in the [PR|https://github.com/jbosstools/jbosstools-openshift/pull/1772] for JBIDE-25700 *# ASSERT: make sure you have an app with a pod running in OpenShift *# EXEC: open OpenShift preferences and point it to an oc that is a bogus executable file (that you created ex. by doing "touch oc && chmod +x oc") * Port Log: *# EXEC: in OpenShift Explorer: select the pod and pick "Pod Log..." *# Result: The "Console" view shows up but nothing happens, there's no output. !pod-log-console-empty.png! * Port Forwarding: *# EXEC: in OpenShift Explorer: select the pod and pick "Port Forwarding..." *# ASSERT: Port Forwarding wizard shows up listing the forwardable ports, the "Status" column shows them "Stopped" *# EXEC: hit "Start All" button *# Result: Port forwarding is not started, the "Status" column for the ports stays "Stopped" !port-forwarding-stopped.png! was: * setup: *# ASSERT: use the code that in the [PR|https://github.com/jbosstools/jbosstools-openshift/pull/1772] for JBIDE-25700 *# ASSERT: make sure you have an app with a pod running in OpenShift *# EXEC: open OpenShift preferences and point it to an oc that is a bogus executable file (that you created ex. by doing "touch oc && chmod +x oc") * Port Log: *# EXEC: in OpenShift Explorer: select the pod and pick "Pod Log..." *# Result: The "Console" view shows up but nothing happens, there's no output. !pod-log-console-empty.png! * Port Forwarding: *# EXEC: in OpenShift Explorer: select the pod and pick "Port Forwarding..." *# ASSERT: Port Forwarding wizard shows up listing the forwardable ports, the "Status" column shows them "Stopped" *# EXEC: hit "Start All" button *# Result: Port forwarding is not started, the "Status" column for the ports stays "Stopped" !port-forwarding-stopped.png! > Pod Log, Port Forwarding: when using bogus oc, log console shows up empty & port forwarding isn't functioning > ------------------------------------------------------------------------------------------------------------- > > Key: JBIDE-26204 > URL: https://issues.jboss.org/browse/JBIDE-26204 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.6.0.Final > Reporter: Andre Dietisheim > Assignee: Andre Dietisheim > Fix For: 4.9.0.AM1 > > Attachments: pod-log-console-empty.png, port-forwarding-stopped.png > > > * Setup: > *# ASSERT: use the code that in the [PR|https://github.com/jbosstools/jbosstools-openshift/pull/1772] for JBIDE-25700 > *# ASSERT: make sure you have an app with a pod running in OpenShift > *# EXEC: open OpenShift preferences and point it to an oc that is a bogus executable file (that you created ex. by doing "touch oc && chmod +x oc") > * Port Log: > *# EXEC: in OpenShift Explorer: select the pod and pick "Pod Log..." > *# Result: > The "Console" view shows up but nothing happens, there's no output. > !pod-log-console-empty.png! > * Port Forwarding: > *# EXEC: in OpenShift Explorer: select the pod and pick "Port Forwarding..." > *# ASSERT: Port Forwarding wizard shows up listing the forwardable ports, the "Status" column shows them "Stopped" > *# EXEC: hit "Start All" button > *# Result: > Port forwarding is not started, the "Status" column for the ports stays "Stopped" > !port-forwarding-stopped.png! -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 8 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-26204) Pod Log, Port Forwarding: when using bogus oc, log console shows up empty & port forwarding isn't functioning

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-26204?page=com.atlassian.jira.plugi... ] Andre Dietisheim updated JBIDE-26204: ------------------------------------- Summary: Pod Log, Port Forwarding: when using bogus oc, log console shows up empty & port forwarding isn't functioning (was: Pod Log, Port Forwarding: log console shows up empty & port forwarding isn't functioning when you use a bogus oc executable) > Pod Log, Port Forwarding: when using bogus oc, log console shows up empty & port forwarding isn't functioning > ------------------------------------------------------------------------------------------------------------- > > Key: JBIDE-26204 > URL: https://issues.jboss.org/browse/JBIDE-26204 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.6.0.Final > Reporter: Andre Dietisheim > Assignee: Andre Dietisheim > Fix For: 4.9.0.AM1 > > Attachments: pod-log-console-empty.png, port-forwarding-stopped.png > > > * setup: > *# ASSERT: use the code that in the [PR|https://github.com/jbosstools/jbosstools-openshift/pull/1772] for JBIDE-25700 > *# ASSERT: make sure you have an app with a pod running in OpenShift > *# EXEC: open OpenShift preferences and point it to an oc that is a bogus executable file (that you created ex. by doing "touch oc && chmod +x oc") > * Port Log: > *# EXEC: in OpenShift Explorer: select the pod and pick "Pod Log..." > *# Result: > The "Console" view shows up but nothing happens, there's no output. > !pod-log-console-empty.png! > * Port Forwarding: > *# EXEC: in OpenShift Explorer: select the pod and pick "Port Forwarding..." > *# ASSERT: Port Forwarding wizard shows up listing the forwardable ports, the "Status" column shows them "Stopped" > *# EXEC: hit "Start All" button > *# Result: > Port forwarding is not started, the "Status" column for the ports stays "Stopped" > !port-forwarding-stopped.png! -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 8 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-26204) Pod Log, Port Forwarding: log console shows up empty & port forwarding isn't functioning when you use a bogus oc executable

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-26204?page=com.atlassian.jira.plugi... ] Andre Dietisheim updated JBIDE-26204: ------------------------------------- Description: * setup: *# ASSERT: use the code that in the [PR|https://github.com/jbosstools/jbosstools-openshift/pull/1772] for JBIDE-25700 *# ASSERT: make sure you have an app with a pod running in OpenShift *# EXEC: open OpenShift preferences and point it to an oc that is a bogus executable file (that you created ex. by doing "touch oc && chmod +x oc") * Port Log: *# EXEC: in OpenShift Explorer: select the pod and pick "Pod Log..." *# Result: The "Console" view shows up but nothing happens, there's no output. !pod-log-console-empty.png! * Port Forwarding: *# EXEC: in OpenShift Explorer: select the pod and pick "Port Forwarding..." *# ASSERT: Port Forwarding wizard shows up listing the forwardable ports, the "Status" column shows them "Stopped" *# EXEC: hit "Start All" button *# Result: Port forwarding is not started, the "Status" column for the ports stays "Stopped" !port-forwarding-stopped.png! was: steps: # ASSERT: use the code that in the [PR|https://github.com/jbosstools/jbosstools-openshift/pull/1772] for JBIDE-25700 # ASSERT: make sure you have an app with a pod running in OpenShift # EXEC: open OpenShift preferences and point it to an oc that is a bogus executable file (that you created ex. by doing "touch oc && chmod +x oc") # EXEC: in OpenShift Explorer: select the pod and pick "Pod Log..." Result: The "Console" view shows up but nothing happens, there's no output. > Pod Log, Port Forwarding: log console shows up empty & port forwarding isn't functioning when you use a bogus oc executable > --------------------------------------------------------------------------------------------------------------------------- > > Key: JBIDE-26204 > URL: https://issues.jboss.org/browse/JBIDE-26204 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.6.0.Final > Reporter: Andre Dietisheim > Assignee: Andre Dietisheim > Fix For: 4.9.0.AM1 > > Attachments: pod-log-console-empty.png, port-forwarding-stopped.png > > > * setup: > *# ASSERT: use the code that in the [PR|https://github.com/jbosstools/jbosstools-openshift/pull/1772] for JBIDE-25700 > *# ASSERT: make sure you have an app with a pod running in OpenShift > *# EXEC: open OpenShift preferences and point it to an oc that is a bogus executable file (that you created ex. by doing "touch oc && chmod +x oc") > * Port Log: > *# EXEC: in OpenShift Explorer: select the pod and pick "Pod Log..." > *# Result: > The "Console" view shows up but nothing happens, there's no output. > !pod-log-console-empty.png! > * Port Forwarding: > *# EXEC: in OpenShift Explorer: select the pod and pick "Port Forwarding..." > *# ASSERT: Port Forwarding wizard shows up listing the forwardable ports, the "Status" column shows them "Stopped" > *# EXEC: hit "Start All" button > *# Result: > Port forwarding is not started, the "Status" column for the ports stays "Stopped" > !port-forwarding-stopped.png! -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 8 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-26204) Pod Log, Port Forwarding: log console shows up empty & port forwarding isn't functioning when you use a bogus oc executable

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-26204?page=com.atlassian.jira.plugi... ] Andre Dietisheim updated JBIDE-26204: ------------------------------------- Attachment: pod-log-console-empty.png > Pod Log, Port Forwarding: log console shows up empty & port forwarding isn't functioning when you use a bogus oc executable > --------------------------------------------------------------------------------------------------------------------------- > > Key: JBIDE-26204 > URL: https://issues.jboss.org/browse/JBIDE-26204 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.6.0.Final > Reporter: Andre Dietisheim > Assignee: Andre Dietisheim > Fix For: 4.9.0.AM1 > > Attachments: pod-log-console-empty.png, port-forwarding-stopped.png > > > steps: > # ASSERT: use the code that in the [PR|https://github.com/jbosstools/jbosstools-openshift/pull/1772] for JBIDE-25700 > # ASSERT: make sure you have an app with a pod running in OpenShift > # EXEC: open OpenShift preferences and point it to an oc that is a bogus executable file (that you created ex. by doing "touch oc && chmod +x oc") > # EXEC: in OpenShift Explorer: select the pod and pick "Pod Log..." > Result: > The "Console" view shows up but nothing happens, there's no output. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 8 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-26204) Pod Log, Port Forwarding: log console shows up empty & port forwarding isn't functioning when you use a bogus oc executable

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-26204?page=com.atlassian.jira.plugi... ] Andre Dietisheim updated JBIDE-26204: ------------------------------------- Attachment: port-forwarding-stopped.png > Pod Log, Port Forwarding: log console shows up empty & port forwarding isn't functioning when you use a bogus oc executable > --------------------------------------------------------------------------------------------------------------------------- > > Key: JBIDE-26204 > URL: https://issues.jboss.org/browse/JBIDE-26204 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.6.0.Final > Reporter: Andre Dietisheim > Assignee: Andre Dietisheim > Fix For: 4.9.0.AM1 > > Attachments: pod-log-console-empty.png, port-forwarding-stopped.png > > > steps: > # ASSERT: use the code that in the [PR|https://github.com/jbosstools/jbosstools-openshift/pull/1772] for JBIDE-25700 > # ASSERT: make sure you have an app with a pod running in OpenShift > # EXEC: open OpenShift preferences and point it to an oc that is a bogus executable file (that you created ex. by doing "touch oc && chmod +x oc") > # EXEC: in OpenShift Explorer: select the pod and pick "Pod Log..." > Result: > The "Console" view shows up but nothing happens, there's no output. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 8 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-26204) Pod Log, Port Forwarding: log console shows up empty & port forwarding isn't functioning when you use a bogus oc executable

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-26204?page=com.atlassian.jira.plugi... ] Andre Dietisheim updated JBIDE-26204: ------------------------------------- Summary: Pod Log, Port Forwarding: log console shows up empty & port forwarding isn't functioning when you use a bogus oc executable (was: Pod Log: console shows up empty when you use a bogus oc executable) > Pod Log, Port Forwarding: log console shows up empty & port forwarding isn't functioning when you use a bogus oc executable > --------------------------------------------------------------------------------------------------------------------------- > > Key: JBIDE-26204 > URL: https://issues.jboss.org/browse/JBIDE-26204 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.6.0.Final > Reporter: Andre Dietisheim > Assignee: Andre Dietisheim > Fix For: 4.9.0.AM1 > > > steps: > # ASSERT: use the code that in the [PR|https://github.com/jbosstools/jbosstools-openshift/pull/1772] for JBIDE-25700 > # ASSERT: make sure you have an app with a pod running in OpenShift > # EXEC: open OpenShift preferences and point it to an oc that is a bogus executable file (that you created ex. by doing "touch oc && chmod +x oc") > # EXEC: in OpenShift Explorer: select the pod and pick "Pod Log..." > Result: > The "Console" view shows up but nothing happens, there's no output. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 8 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-26140) Remove unit testing related jars from SSP distribution

by Rob Stryker (JIRA)

[ https://issues.jboss.org/browse/JBIDE-26140?page=com.atlassian.jira.plugi... ] Rob Stryker resolved JBIDE-26140. --------------------------------- Resolution: Done These jars are no longer in distribution. > Remove unit testing related jars from SSP distribution > ------------------------------------------------------ > > Key: JBIDE-26140 > URL: https://issues.jboss.org/browse/JBIDE-26140 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: stack-server-protocol > Reporter: Denis Golovin > Assignee: Rob Stryker > Fix For: 4.6.0.Final > > Attachments: ssp-distribution.png > > > The size of zipped distribution is around 30MB. Could be less if unit test related jars like hamcrest or assertj are not included. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 8 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-26140) Remove unit testing related jars from SSP distribution

by Rob Stryker (JIRA)

[ https://issues.jboss.org/browse/JBIDE-26140?page=com.atlassian.jira.plugi... ] Rob Stryker updated JBIDE-26140: -------------------------------- Fix Version/s: 4.6.0.Final > Remove unit testing related jars from SSP distribution > ------------------------------------------------------ > > Key: JBIDE-26140 > URL: https://issues.jboss.org/browse/JBIDE-26140 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: stack-server-protocol > Reporter: Denis Golovin > Assignee: Rob Stryker > Fix For: 4.6.0.Final > > Attachments: ssp-distribution.png > > > The size of zipped distribution is around 30MB. Could be less if unit test related jars like hamcrest or assertj are not included. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 8 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 2018