[JBoss JIRA] (JBIDE-22153) Closing log of a pod throws an exception
by Marián Labuda (JIRA)
[ https://issues.jboss.org/browse/JBIDE-22153?page=com.atlassian.jira.plugi... ]
Marián Labuda closed JBIDE-22153.
---------------------------------
Verified in JBDS 10.0.0.Alpha1 B5207.
> Closing log of a pod throws an exception
> ----------------------------------------
>
> Key: JBIDE-22153
> URL: https://issues.jboss.org/browse/JBIDE-22153
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: openshift
> Affects Versions: 4.3.1.CR1
> Reporter: Marián Labuda
> Assignee: Viacheslav Kabanovich
> Labels: openshift_v3
> Fix For: 4.4.0.Alpha1
>
>
> When I am trying to close log of a pod (build pod or application pod, does not matter which one) by clicking on gray view tool item Close, I get following exception
> {code}
> Exception reading pod log inputstream
> java.io.IOException: Stream closed
> at java.io.BufferedInputStream.getBufIfOpen(BufferedInputStream.java:170)
> at java.io.BufferedInputStream.read(BufferedInputStream.java:336)
> at java.io.SequenceInputStream.read(SequenceInputStream.java:207)
> at java.io.BufferedInputStream.read1(BufferedInputStream.java:284)
> at java.io.BufferedInputStream.read(BufferedInputStream.java:345)
> at java.io.FilterInputStream.read(FilterInputStream.java:107)
> at org.jboss.tools.openshift.internal.ui.job.PodLogsJob$ConsoleStreamPipe.runOCBinary(PodLogsJob.java:166)
> at org.jboss.tools.openshift.internal.core.OCBinaryOperation.run(OCBinaryOperation.java:34)
> at org.jboss.tools.openshift.internal.ui.job.PodLogsJob$ConsoleStreamPipe.run(PodLogsJob.java:153)
> at java.lang.Thread.run(Thread.java:745)
> {code}
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 11 months
[JBoss JIRA] (ERT-155) Expose DockerContainerConfig#labels() in API [EBZ#485936]
by Friendly Jira Robot (JIRA)
Friendly Jira Robot created ERT-155:
---------------------------------------
Summary: Expose DockerContainerConfig#labels() in API [EBZ#485936]
Key: ERT-155
URL: https://issues.jboss.org/browse/ERT-155
Project: Eclipse Release Train
Issue Type: Task
Components: Linux Tools
Reporter: Friendly Jira Robot
This method is implemented in DockerContainerConfig but not exposed in the API (it was implemented for Linux Tools 4.2.1 which did not allow for API changes)
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 11 months
[JBoss JIRA] (ERT-156) Docker host ip cannot be copied to clipboard from anywhere [EBZ#487035]
by Friendly Jira Robot (JIRA)
Friendly Jira Robot created ERT-156:
---------------------------------------
Summary: Docker host ip cannot be copied to clipboard from anywhere [EBZ#487035]
Key: ERT-156
URL: https://issues.jboss.org/browse/ERT-156
Project: Eclipse Release Train
Issue Type: Task
Components: Linux Tools
Reporter: Friendly Jira Robot
It would be nice if you could copy the docker host ip from somewhere.
Currently when you create a docker connection to a docker host (using Docker Machine on Mac or similar), in Docker Explorer, you see the url next to the connection name. But there is no way to copy the ip.
Currently it's not listed in the connection properties in Properties view either. I think this would be the easiest place to get it - at least show it in the Properties view so it's ready for copying to clipboard.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 11 months
[JBoss JIRA] (ERT-157) IOException below ShowInSystemExplorerCommandHandler.getLaunchProcess [EBZ#490064]
by Friendly Jira Robot (JIRA)
Friendly Jira Robot created ERT-157:
---------------------------------------
Summary: IOException below ShowInSystemExplorerCommandHandler.getLaunchProcess [EBZ#490064]
Key: ERT-157
URL: https://issues.jboss.org/browse/ERT-157
Project: Eclipse Release Train
Issue Type: Task
Components: Linux Tools
Reporter: Friendly Jira Robot
The following incident was reported via the automated error reporting:
code: 4
plugin: org.eclipse.linuxtools.docker.ui_1.2.1.201602162146
message: Failed to open in Web Browser
fingerprint: fa87658c7f9f2a929e575abadbd968e0
exception class: java.io.IOException
exception message: Cannot run program "explorer" (in directory "\users\rodriguj\docker"): CreateProcess error=267, The directory name is invalid
number of children: 0
java.io.IOException: Cannot run program "explorer" (in directory "\users\rodriguj\docker"): CreateProcess error=267, The directory name is invalid
at java.lang.ProcessBuilder.start(null:-1)
at java.lang.Runtime.exec(null:-1)
at java.lang.Runtime.exec(null:-1)
at org.eclipse.linuxtools.internal.docker.ui.commands.ShowInSystemExplorerCommandHandler.getLaunchProcess(ShowInSystemExplorerCommandHandler.java:102)[REQUIRED]
at org.eclipse.linuxtools.internal.docker.ui.commands.ShowInSystemExplorerCommandHandler.access$0(ShowInSystemExplorerCommandHandler.java:96)
at org.eclipse.linuxtools.internal.docker.ui.commands.ShowInSystemExplorerCommandHandler$1.run(ShowInSystemExplorerCommandHandler.java:65)
at org.eclipse.core.internal.jobs.Worker.run(Worker.java:55)
caused by: java.io.IOException: CreateProcess error=267, The directory name is invalid
at java.lang.ProcessImpl.create(null:-2)[REQUIRED, TOPMOST]
at java.lang.ProcessImpl.<init>(null:-1)
at java.lang.ProcessImpl.start(null:-1)
at java.lang.ProcessBuilder.start(null:-1)
at java.lang.Runtime.exec(null:-1)
at java.lang.Runtime.exec(null:-1)
at org.eclipse.linuxtools.internal.docker.ui.commands.ShowInSystemExplorerCommandHandler.getLaunchProcess(ShowInSystemExplorerCommandHandler.java:102)[REQUIRED]
at org.eclipse.linuxtools.internal.docker.ui.commands.ShowInSystemExplorerCommandHandler.access$0(ShowInSystemExplorerCommandHandler.java:96)
at org.eclipse.linuxtools.internal.docker.ui.commands.ShowInSystemExplorerCommandHandler$1.run(ShowInSystemExplorerCommandHandler.java:65)
at org.eclipse.core.internal.jobs.Worker.run(Worker.java:55)
General Information:
reported-by: -
anonymous-id: 9174a056-8381-4e87-a9ff-6cdc8dad0c76
eclipse-build-id: 4.5.2.M20160212-1500
eclipse-product: org.eclipse.epp.package.java.product
operating system: Windows7 6.1.0 (x86_64) - win32
jre-version: 1.8.0_73-b02
The following plug-ins were present on the execution stack (*):
1. org.eclipse.core.jobs_3.7.0.v20150330-2103
2. org.eclipse.linuxtools.docker.ui_1.2.1.201602162146
Please note that:
* Messages, stacktraces, and nested status objects may be shortened.
* Bug fields like status, resolution, and whiteboard are sent
back to reporters.
* The list of present bundles and their respective versions was
calculated by package naming heuristics. This may or may not reflect reality.
Other Resources:
* Report: https://dev.eclipse.org/recommenders/committers/confess/#/problems/56eaaa...
* Manual: https://dev.eclipse.org/recommenders/community/confess/#/guide
Thank you for your assistance.
Your friendly error-reports-inbox.
This bug was created on behalf of xcoulon@xxxxxxxxxxxx.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 11 months