[JBoss JIRA] (JBIDE-26043) Two paths to OC client in properties view for OpenShift connection
by Josef Kopriva (JIRA)
[ https://issues.jboss.org/browse/JBIDE-26043?page=com.atlassian.jira.plugi... ]
Josef Kopriva commented on JBIDE-26043:
---------------------------------------
[~adietish] If you set "Override OC connection", then you have two paths. But if you uncheck "Override OC connection", you still have two paths - one is correct, one is wrong.
!screenshot-4.png|thumbnail!
> Two paths to OC client in properties view for OpenShift connection
> ------------------------------------------------------------------
>
> Key: JBIDE-26043
> URL: https://issues.jboss.org/browse/JBIDE-26043
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: openshift
> Affects Versions: 4.6.0.AM2
> Reporter: Josef Kopriva
> Priority: Minor
> Labels: oc_binary, properties
> Fix For: 4.6.x
>
> Attachments: image-2018-05-28-14-48-08-877.png, screenshot-1.png, screenshot-2.png, screenshot-3.png, screenshot-4.png
>
>
> !image-2018-05-28-14-48-08-877.png|thumbnail!
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
7 years, 10 months
[JBoss JIRA] (JBIDE-25861) Docker connection throws DockerTimeoutException with warning in error log when CDK is stopped
by Jeff Johnston (JIRA)
[ https://issues.jboss.org/browse/JBIDE-25861?page=com.atlassian.jira.plugi... ]
Jeff Johnston commented on JBIDE-25861:
---------------------------------------
Yes, a log message was not passing the connection uri. Log message will be fixed in tonight's build and will be part of Photon RC2 milestone. Thanks.
> Docker connection throws DockerTimeoutException with warning in error log when CDK is stopped
> ---------------------------------------------------------------------------------------------
>
> Key: JBIDE-25861
> URL: https://issues.jboss.org/browse/JBIDE-25861
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: cdk, docker
> Affects Versions: 4.5.3.AM3
> Environment: Fedora 27 x86_64
> Reporter: Ondrej Dockal
> Assignee: Jeff Johnston
> Labels: upstream
> Fix For: 4.6.0.AM1
>
>
> After the docker connection is interrupted by force, there is written to console endless output from docker connection:
> {code}
> Mar 26, 2018 11:39:08 PM org.apache.http.impl.execchain.RetryExec execute
> INFO: Retrying request to {}->unix://localhost:80
> Mar 26, 2018 11:39:08 PM org.apache.http.impl.execchain.RetryExec execute
> INFO: I/O exception (java.io.IOException) caught when processing request to {}->unix://localhost:80: No such file or directory
> Mar 26, 2018 11:39:08 PM org.apache.http.impl.execchain.RetryExec execute
> INFO: Retrying request to {}->unix://localhost:80
> Mar 26, 2018 11:39:08 PM org.apache.http.impl.execchain.RetryExec execute
> INFO: I/O exception (java.io.IOException) caught when processing request to {}->unix://localhost:80: No such file or directory
> Mar 26, 2018 11:39:08 PM org.apache.http.impl.execchain.RetryExec execute
> INFO: Retrying request to {}->unix://localhost:80
> Mar 26, 2018 11:39:08 PM org.apache.http.impl.execchain.RetryExec execute
> INFO: I/O exception (java.io.IOException) caught when processing request to {}->unix://localhost:80: No such file or directory
> {code}
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
7 years, 10 months
[JBoss JIRA] (JBIDE-24318) Analyze watch replacement
by Andre Dietisheim (JIRA)
[ https://issues.jboss.org/browse/JBIDE-24318?page=com.atlassian.jira.plugi... ]
Andre Dietisheim edited comment on JBIDE-24318 at 5/29/18 9:52 AM:
-------------------------------------------------------------------
resolved & reopened to clear "Coding in Progress".
It's very likely that this wont happen since we decided to put JBoss Tools Eclipse into maintenance mode. Moving fix-version to LATER.
was (Author: adietish):
resolved & reopened to clear "Coding in Progress".
This very likely wont happen since we decided to move JBoss Tools Eclipse into maintenance mode.
> Analyze watch replacement
> -------------------------
>
> Key: JBIDE-24318
> URL: https://issues.jboss.org/browse/JBIDE-24318
> Project: Tools (JBoss Tools)
> Issue Type: Task
> Components: openshift
> Reporter: Jeff MAURY
> Assignee: Dmitrii Bocharov
> Labels: openshift, openshift_v3
> Fix For: LATER
>
>
> Analyze how the watch and watch manager can be implemented when switching to the fabric8 client
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
7 years, 10 months
[JBoss JIRA] (JBIDE-24316) Analyze connection management
by Andre Dietisheim (JIRA)
[ https://issues.jboss.org/browse/JBIDE-24316?page=com.atlassian.jira.plugi... ]
Andre Dietisheim commented on JBIDE-24316:
------------------------------------------
It's very likely that this wont happen since we decided to put JBoss Tools Eclipse into maintenance mode. Moving fix-version to LATER.
> Analyze connection management
> -----------------------------
>
> Key: JBIDE-24316
> URL: https://issues.jboss.org/browse/JBIDE-24316
> Project: Tools (JBoss Tools)
> Issue Type: Task
> Components: openshift
> Reporter: Jeff MAURY
> Labels: openshift, openshift_v3
> Fix For: LATER
>
>
> Analyze connection management: is connection/client accessible from resources like it is for the REST client or is there a new pattern needed
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
7 years, 10 months