[JBoss JIRA] (JBIDE-22693) Label for editing name of property in design view is too short. Name seems to be cut.
by Viacheslav Kabanovich (JIRA)
[ https://issues.jboss.org/browse/JBIDE-22693?page=com.atlassian.jira.plugi... ]
Viacheslav Kabanovich commented on JBIDE-22693:
-----------------------------------------------
[~odockal], is the table width is divided equally between Name and Value when editor is opened? Could you please add a screenshot? It is possible to give assign more space to Name, but then value will not have it enough.
> Label for editing name of property in design view is too short. Name seems to be cut.
> -------------------------------------------------------------------------------------
>
> Key: JBIDE-22693
> URL: https://issues.jboss.org/browse/JBIDE-22693
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: xml-structured-editor
> Environment: devstudio:
> Version: 10.0.1.AM1
> Build id: v20160613-2041
> Fedora 24, x86_64
> Reporter: Ondrej Dockal
> Assignee: Viacheslav Kabanovich
> Fix For: 4.4.x
>
> Attachments: DesignView1_Batch.png, DesignView2_Batch.png
>
>
> Implies to editing label component in all property tables.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 9 months
[JBoss JIRA] (JBIDE-22693) Label for editing name of property in design view is too short. Name seems to be cut.
by Viacheslav Kabanovich (JIRA)
[ https://issues.jboss.org/browse/JBIDE-22693?page=com.atlassian.jira.plugi... ]
Viacheslav Kabanovich edited comment on JBIDE-22693 at 7/7/16 10:07 PM:
------------------------------------------------------------------------
[~odockal], is the table width is divided equally between Name and Value when editor is opened? Could you please add a screenshot? It is possible to assign more space to Name, but then value will not have it enough.
was (Author: scabanovich):
[~odockal], is the table width is divided equally between Name and Value when editor is opened? Could you please add a screenshot? It is possible to give assign more space to Name, but then value will not have it enough.
> Label for editing name of property in design view is too short. Name seems to be cut.
> -------------------------------------------------------------------------------------
>
> Key: JBIDE-22693
> URL: https://issues.jboss.org/browse/JBIDE-22693
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: xml-structured-editor
> Environment: devstudio:
> Version: 10.0.1.AM1
> Build id: v20160613-2041
> Fedora 24, x86_64
> Reporter: Ondrej Dockal
> Assignee: Viacheslav Kabanovich
> Fix For: 4.4.x
>
> Attachments: DesignView1_Batch.png, DesignView2_Batch.png
>
>
> Implies to editing label component in all property tables.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 9 months
[JBoss JIRA] (JBIDE-22627) Docker image tag is ignored in Deploy Image to OpenShift wizard
by Viacheslav Kabanovich (JIRA)
[ https://issues.jboss.org/browse/JBIDE-22627?page=com.atlassian.jira.plugi... ]
Viacheslav Kabanovich commented on JBIDE-22627:
-----------------------------------------------
[~fbricon], please take a look at the pull request.
> Docker image tag is ignored in Deploy Image to OpenShift wizard
> ---------------------------------------------------------------
>
> Key: JBIDE-22627
> URL: https://issues.jboss.org/browse/JBIDE-22627
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: openshift
> Affects Versions: 4.4.0.Final
> Reporter: Marián Labuda
> Labels: docker, openshift_v3
> Fix For: 4.4.1.AM2
>
> Attachments: docker_explorer.png
>
>
> When deploying a docker image from docker explorer by selecting context menu item Deploy to OpenShift..., image name in opened Deploy Image to OpenShift wizard does not contain tag of the image. This requires manual addition of image tag, otherwise latest tag is presumed by default, what does not have to be desired at some scenarios.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 9 months
[JBoss JIRA] (JBIDE-22691) Allow extensions to be injected with Eclipse services
by Alexey Kazakov (JIRA)
[ https://issues.jboss.org/browse/JBIDE-22691?page=com.atlassian.jira.plugi... ]
Alexey Kazakov commented on JBIDE-22691:
----------------------------------------
[~jsteele] please add some javadoc with usage examples of this code then we can resolve the issue.
+1 to contribute it to Eclipse Platform. But please create a new issue in our JIRA to track that contribution. We will need to remove this from our plugin if we have it contribute to Eclipse.
And as we have already discussed a blog post is welcome ;)
> Allow extensions to be injected with Eclipse services
> -----------------------------------------------------
>
> Key: JBIDE-22691
> URL: https://issues.jboss.org/browse/JBIDE-22691
> Project: Tools (JBoss Tools)
> Issue Type: Enhancement
> Components: common/jst/core
> Affects Versions: 4.4.1.AM1
> Reporter: John Steele
> Assignee: John Steele
> Fix For: 4.4.x
>
>
> We need a way to share services with extensions.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 9 months
[JBoss JIRA] (JBIDE-22677) rsync stuck on OSX
by Alexey Kazakov (JIRA)
[ https://issues.jboss.org/browse/JBIDE-22677?page=com.atlassian.jira.plugi... ]
Alexey Kazakov updated JBIDE-22677:
-----------------------------------
Fix Version/s: 4.4.x
> rsync stuck on OSX
> ------------------
>
> Key: JBIDE-22677
> URL: https://issues.jboss.org/browse/JBIDE-22677
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: openshift
> Reporter: Fred Bricon
> Assignee: Dmitry Bocharov
> Priority: Blocker
> Fix For: 4.4.x
>
>
> I deployed an eap app from the eap64-basic-s2i template, then created an openshift 3 server.
> On server startup, publishing fails to complete after 5 minutes and a thread dump shows rsync is still blocking in the background.
> {noformat}
> "pool-40-thread-1" #231 prio=5 os_prio=31 tid=0x00007f9a55dd0000 nid=0xeb9f runnable [0x000000013199a000]
> java.lang.Thread.State: RUNNABLE
> at java.io.FileInputStream.readBytes(Native Method)
> at java.io.FileInputStream.read(FileInputStream.java:255)
> at java.io.BufferedInputStream.read1(BufferedInputStream.java:284)
> at java.io.BufferedInputStream.read(BufferedInputStream.java:345)
> - locked <0x00000007b3d45cb8> (a java.lang.UNIXProcess$ProcessPipeInputStream)
> at sun.nio.cs.StreamDecoder.readBytes(StreamDecoder.java:284)
> at sun.nio.cs.StreamDecoder.implRead(StreamDecoder.java:326)
> at sun.nio.cs.StreamDecoder.read(StreamDecoder.java:178)
> - locked <0x00000007b3d49d50> (a java.io.InputStreamReader)
> at java.io.InputStreamReader.read(InputStreamReader.java:184)
> at java.io.BufferedReader.fill(BufferedReader.java:161)
> at java.io.BufferedReader.readLine(BufferedReader.java:324)
> - locked <0x00000007b3d49d50> (a java.io.InputStreamReader)
> at java.io.BufferedReader.readLine(BufferedReader.java:389)
> at org.jboss.tools.openshift.core.server.RSync.lambda$0(RSync.java:152)
> at org.jboss.tools.openshift.core.server.RSync$$Lambda$181/1635081930.run(Unknown Source)
> at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142)
> at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)
> at java.lang.Thread.run(Thread.java:745)
> I'm deploying on CDK 2.1RC5
> {noformat}
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 9 months
[JBoss JIRA] (JBIDE-22686) Can't push image to docker registry
by Alexey Kazakov (JIRA)
[ https://issues.jboss.org/browse/JBIDE-22686?page=com.atlassian.jira.plugi... ]
Alexey Kazakov updated JBIDE-22686:
-----------------------------------
Fix Version/s: 4.4.x
> Can't push image to docker registry
> -----------------------------------
>
> Key: JBIDE-22686
> URL: https://issues.jboss.org/browse/JBIDE-22686
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: docker, openshift
> Affects Versions: 4.4.0.Final
> Environment: Fedora 23
> Reporter: Dmitry Bocharov
> Assignee: Dmitry Bocharov
> Fix For: 4.4.x
>
> Attachments: DeployDockerImageToOS.webm
>
>
> The screencast of the last steps is attached.
> Properties and settings of the cdk haven't been changed. Everything is dowloaded and installed in a usual way.
> Possibly something is with the dns - maybe it wasn't configured correctly while cdk installation. Because we to push to the valid url, while OS connection only an IP in its settings.
> _exception:_
> org.eclipse.linuxtools.docker.core.DockerException: com.spotify.docker.client.DockerException: org.eclipse.linuxtools.docker.core.DockerImagePushFailedException: Image push failed: hub.openshift.rhel-cdk.10.1.2.2.xip.io/sample-project/aloha: unable to ping registry endpoint https://hub.openshift.rhel-cdk.10.1.2.2.xip.io/v0/
> v2 ping attempt failed with error: Get https://hub.openshift.rhel-cdk.10.1.2.2.xip.io/v2/: dial tcp 10.1.2.2:443: connection refused
> v1 ping attempt failed with error: Get https://hub.openshift.rhel-cdk.10.1.2.2.xip.io/v1/_ping: dial tcp 10.1.2.2:443: connection refused
> at org.eclipse.linuxtools.internal.docker.core.DockerConnection.pushImage(DockerConnection.java:1047)
> at org.jboss.tools.openshift.internal.ui.dockerutils.PushImageToRegistryJob.doRun(PushImageToRegistryJob.java:67)
> at org.jboss.tools.openshift.internal.common.core.job.AbstractDelegatingMonitorJob.run(AbstractDelegatingMonitorJob.java:37)
> at org.eclipse.core.internal.jobs.Worker.run(Worker.java:55)
> Caused by: com.spotify.docker.client.DockerException: org.eclipse.linuxtools.docker.core.DockerImagePushFailedException: Image push failed: hub.openshift.rhel-cdk.10.1.2.2.xip.io/sample-project/aloha: unable to ping registry endpoint https://hub.openshift.rhel-cdk.10.1.2.2.xip.io/v0/
> v2 ping attempt failed with error: Get https://hub.openshift.rhel-cdk.10.1.2.2.xip.io/v2/: dial tcp 10.1.2.2:443: connection refused
> v1 ping attempt failed with error: Get https://hub.openshift.rhel-cdk.10.1.2.2.xip.io/v1/_ping: dial tcp 10.1.2.2:443: connection refused
> at org.eclipse.linuxtools.internal.docker.core.DockerProgressHandler.progress(DockerProgressHandler.java:42)
> at com.spotify.docker.client.ProgressStream.tail(ProgressStream.java:74)
> at com.spotify.docker.client.DefaultDockerClient.push(DefaultDockerClient.java:821)
> at org.eclipse.linuxtools.internal.docker.core.DockerConnection.pushImage(DockerConnection.java:1043)
> ... 3 more
> Caused by: org.eclipse.linuxtools.docker.core.DockerImagePushFailedException: Image push failed: hub.openshift.rhel-cdk.10.1.2.2.xip.io/sample-project/aloha: unable to ping registry endpoint https://hub.openshift.rhel-cdk.10.1.2.2.xip.io/v0/
> v2 ping attempt failed with error: Get https://hub.openshift.rhel-cdk.10.1.2.2.xip.io/v2/: dial tcp 10.1.2.2:443: connection refused
> v1 ping attempt failed with error: Get https://hub.openshift.rhel-cdk.10.1.2.2.xip.io/v1/_ping: dial tcp 10.1.2.2:443: connection refused
> at org.eclipse.linuxtools.internal.docker.ui.views.ImagePushProgressHandler.processMessage(ImagePushProgressHandler.java:49)
> at org.eclipse.linuxtools.internal.docker.core.DockerProgressHandler.progress(DockerProgressHandler.java:40)
> ... 6 more
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 9 months