[JBoss JIRA] (JBIDE-21889) Content assist for image names in "Deploy Docker Image" wizard
by Marián Labuda (JIRA)
Marián Labuda created JBIDE-21889:
-------------------------------------
Summary: Content assist for image names in "Deploy Docker Image" wizard
Key: JBIDE-21889
URL: https://issues.jboss.org/browse/JBIDE-21889
Project: Tools (JBoss Tools)
Issue Type: Enhancement
Components: openshift
Affects Versions: 4.3.1.Beta2
Reporter: Xavier Coulon
Assignee: Xavier Coulon
Fix For: 4.3.1.CR1
The {{Image Name}} field could be enhanced with content assist based on the list of image names+tags retrieved from the selected Docker connection.
If the user inputs a name that does not match the list, a warning on the page would inform him/her that a remote call to the registry would be performed upon page completion, ie, when clicking on the {{Next}} button.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years, 1 month
[JBoss JIRA] (JBIDE-21889) Content assist for image names in "Deploy Docker Image" wizard
by Marián Labuda (JIRA)
[ https://issues.jboss.org/browse/JBIDE-21889?page=com.atlassian.jira.plugi... ]
Marián Labuda updated JBIDE-21889:
----------------------------------
Fix Version/s: 4.4.0.Alpha1
(was: 4.3.1.CR1)
> Content assist for image names in "Deploy Docker Image" wizard
> ---------------------------------------------------------------
>
> Key: JBIDE-21889
> URL: https://issues.jboss.org/browse/JBIDE-21889
> Project: Tools (JBoss Tools)
> Issue Type: Enhancement
> Components: openshift
> Affects Versions: 4.3.1.Beta2
> Reporter: Xavier Coulon
> Assignee: Xavier Coulon
> Labels: deploy_docker_wizard, openshift_v3
> Fix For: 4.4.0.Alpha1
>
>
> The {{Image Name}} field could be enhanced with content assist based on the list of image names+tags retrieved from the selected Docker connection.
> If the user inputs a name that does not match the list, a warning on the page would inform him/her that a remote call to the registry would be performed upon page completion, ie, when clicking on the {{Next}} button.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years, 1 month
[JBoss JIRA] (JBIDE-21889) Content assist for image names in "Deploy Docker Image" wizard
by Marián Labuda (JIRA)
[ https://issues.jboss.org/browse/JBIDE-21889?page=com.atlassian.jira.plugi... ]
Marián Labuda resolved JBIDE-21889.
-----------------------------------
Resolution: Done
> Content assist for image names in "Deploy Docker Image" wizard
> ---------------------------------------------------------------
>
> Key: JBIDE-21889
> URL: https://issues.jboss.org/browse/JBIDE-21889
> Project: Tools (JBoss Tools)
> Issue Type: Enhancement
> Components: openshift
> Affects Versions: 4.3.1.Beta2
> Reporter: Xavier Coulon
> Assignee: Xavier Coulon
> Labels: deploy_docker_wizard, openshift_v3
> Fix For: 4.4.0.Alpha1
>
>
> The {{Image Name}} field could be enhanced with content assist based on the list of image names+tags retrieved from the selected Docker connection.
> If the user inputs a name that does not match the list, a warning on the page would inform him/her that a remote call to the registry would be performed upon page completion, ie, when clicking on the {{Next}} button.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years, 1 month
[JBoss JIRA] (JBDS-3684) Preview pane in HTML editor fails with 404 error with OpenJDK
by Ilya Buziuk (JIRA)
[ https://issues.jboss.org/browse/JBDS-3684?page=com.atlassian.jira.plugin.... ]
Ilya Buziuk edited comment on JBDS-3684 at 3/17/16 8:28 AM:
------------------------------------------------------------
[~ldimaggio] HTML preview works fine on Windows 8.1 pro (IE 11) (tested against kitchensink-html5-mobile) !preview.png|thumbnail!
Unfortunately, I do not have windows 10 right now for testing this issue. If it is possible, could you please confirm that this behaviour is Windows 10 specific and not reproducible on Windows 7 / 8 ?
Also, could you please provide more details:
- what version of IE do you have ? (AFAIK, Microsoft Edge is the default browser in Windows 10 but IE should be also available) My guess is that this issue is coupled with browser native render (for html preview SWT.NONE is used which is IE for Windows ), rather than jdk (running against oracle could very likely lead to the same behaviour).
- Is it reproducible on every html file or some specific one ?
Thanks
was (Author: ibuziuk):
[~dimaggio] HTML preview works fine on Windows 8.1 pro (IE 11) (tested against kitchensink-html5-mobile) !preview.png|thumbnail!
Unfortunately, I do not have windows 10 right now for testing this issue. If it is possible, could you please confirm that this behaviour is Windows 10 specific and not reproducible on Windows 7 / 8 ?
Also, could you please provide more details:
- what version of IE do you have ? (AFAIK, Microsoft Edge is the default browser in Windows 10 but IE should be also available) My guess is that this issue is coupled with browser native render (for html preview SWT.NONE is used which is IE for Windows ), rather than jdk (running against oracle could very likely lead to the same behaviour).
- Is it reproducible on every html file or some specific one ?
Thanks
> Preview pane in HTML editor fails with 404 error with OpenJDK
> -------------------------------------------------------------
>
> Key: JBDS-3684
> URL: https://issues.jboss.org/browse/JBDS-3684
> Project: Developer Studio (JBoss Developer Studio)
> Issue Type: Bug
> Components: upstream
> Affects Versions: 9.1.0.CR1
> Reporter: Len DiMaggio
> Assignee: Ilya Buziuk
> Priority: Critical
> Labels: openjdk
> Fix For: 9.1.0.CR1
>
> Attachments: preview.png
>
>
> The editor opens the file, and its palette is displayed - the preview pane shows a 404 error.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years, 1 month
[JBoss JIRA] (JBDS-3684) Preview pane in HTML editor fails with 404 error with OpenJDK
by Ilya Buziuk (JIRA)
[ https://issues.jboss.org/browse/JBDS-3684?page=com.atlassian.jira.plugin.... ]
Ilya Buziuk edited comment on JBDS-3684 at 3/17/16 8:19 AM:
------------------------------------------------------------
[~dimaggio] HTML preview works fine on Windows 8.1 pro (IE 11) (tested against kitchensink-html5-mobile) !preview.png|thumbnail!
Unfortunately, I do not have windows 10 right now for testing this issue. If it is possible, could you please confirm that this behaviour is Windows 10 specific and not reproducible on Windows 7 / 8 ?
Also, could you please provide more details:
- what version of IE do you have ? (AFAIK, Microsoft Edge is the default browser in Windows 10 but IE should be also available) My guess is that this issue is coupled with browser native render (for html preview SWT.NONE is used which is IE for Windows ), rather than jdk (running against oracle could very likely lead to the same behaviour).
- Is it reproducible on every html file or some specific one ?
Thanks
was (Author: ibuziuk):
[~dimaggio] HTML preview works fine on Windows 8.1 pro (IE 11) (tested against kitchensink-html5-mobile) !preview.png|thumbnail!
Unfortunately, I do not have windows 10 right now for testing this issue. If it is possible, could you please confirm that this behaviour is Windows 10 specific and not reproducible on Windows 7 / 8 ?
Also, could you please provide more details:
- what version of IE do you have ? (AFAIK, Microsoft Edge is the default browser in Windows 10 but IE should be also available) My guess is that this issue is coupled with with browser native render (for html preview SWT.NONE is used which is IE for Windows ), rather than jdk (running against oracle could very likely lead to the same behaviour).
- Is it reproducible on every html file or some specific one ?
Thanks
> Preview pane in HTML editor fails with 404 error with OpenJDK
> -------------------------------------------------------------
>
> Key: JBDS-3684
> URL: https://issues.jboss.org/browse/JBDS-3684
> Project: Developer Studio (JBoss Developer Studio)
> Issue Type: Bug
> Components: upstream
> Affects Versions: 9.1.0.CR1
> Reporter: Len DiMaggio
> Assignee: Ilya Buziuk
> Priority: Critical
> Labels: openjdk
> Fix For: 9.1.0.CR1
>
> Attachments: preview.png
>
>
> The editor opens the file, and its palette is displayed - the preview pane shows a 404 error.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years, 1 month
[JBoss JIRA] (JBDS-3684) Preview pane in HTML editor fails with 404 error with OpenJDK
by Ilya Buziuk (JIRA)
[ https://issues.jboss.org/browse/JBDS-3684?page=com.atlassian.jira.plugin.... ]
Ilya Buziuk commented on JBDS-3684:
-----------------------------------
[~dimaggio] HTML preview works fine on Windows 8.1 pro (IE 11) (tested against kitchensink-html5-mobile) !preview.png|thumbnail!
Unfortunately, I do not have windows 10 right now for testing this issue. If it is possible, could you please confirm that this behaviour is Windows 10 specific and not reproducible on Windows 7 / 8 ?
Also, could you please provide more details: - what version of IE do you have ? (AFAIK, Microsoft Edge is the default browser in Windows 10 but IE should be also available) My guess is that this issue is coupled with with browser native render (for html preview SWT.NONE is used which is IE for Windows ), rather than jdk (running against oracle could very likely lead to the same behaviour).
- Is it reproducible on every html file or some specific one ?
Thanks
> Preview pane in HTML editor fails with 404 error with OpenJDK
> -------------------------------------------------------------
>
> Key: JBDS-3684
> URL: https://issues.jboss.org/browse/JBDS-3684
> Project: Developer Studio (JBoss Developer Studio)
> Issue Type: Bug
> Components: upstream
> Affects Versions: 9.1.0.CR1
> Reporter: Len DiMaggio
> Assignee: Ilya Buziuk
> Priority: Critical
> Labels: openjdk
> Fix For: 9.1.0.CR1
>
> Attachments: preview.png
>
>
> The editor opens the file, and its palette is displayed - the preview pane shows a 404 error.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years, 1 month
[JBoss JIRA] (JBDS-3684) Preview pane in HTML editor fails with 404 error with OpenJDK
by Ilya Buziuk (JIRA)
[ https://issues.jboss.org/browse/JBDS-3684?page=com.atlassian.jira.plugin.... ]
Ilya Buziuk edited comment on JBDS-3684 at 3/17/16 8:18 AM:
------------------------------------------------------------
[~dimaggio] HTML preview works fine on Windows 8.1 pro (IE 11) (tested against kitchensink-html5-mobile) !preview.png|thumbnail!
Unfortunately, I do not have windows 10 right now for testing this issue. If it is possible, could you please confirm that this behaviour is Windows 10 specific and not reproducible on Windows 7 / 8 ?
Also, could you please provide more details:
- what version of IE do you have ? (AFAIK, Microsoft Edge is the default browser in Windows 10 but IE should be also available) My guess is that this issue is coupled with with browser native render (for html preview SWT.NONE is used which is IE for Windows ), rather than jdk (running against oracle could very likely lead to the same behaviour).
- Is it reproducible on every html file or some specific one ?
Thanks
was (Author: ibuziuk):
[~dimaggio] HTML preview works fine on Windows 8.1 pro (IE 11) (tested against kitchensink-html5-mobile) !preview.png|thumbnail!
Unfortunately, I do not have windows 10 right now for testing this issue. If it is possible, could you please confirm that this behaviour is Windows 10 specific and not reproducible on Windows 7 / 8 ?
Also, could you please provide more details: - what version of IE do you have ? (AFAIK, Microsoft Edge is the default browser in Windows 10 but IE should be also available) My guess is that this issue is coupled with with browser native render (for html preview SWT.NONE is used which is IE for Windows ), rather than jdk (running against oracle could very likely lead to the same behaviour).
- Is it reproducible on every html file or some specific one ?
Thanks
> Preview pane in HTML editor fails with 404 error with OpenJDK
> -------------------------------------------------------------
>
> Key: JBDS-3684
> URL: https://issues.jboss.org/browse/JBDS-3684
> Project: Developer Studio (JBoss Developer Studio)
> Issue Type: Bug
> Components: upstream
> Affects Versions: 9.1.0.CR1
> Reporter: Len DiMaggio
> Assignee: Ilya Buziuk
> Priority: Critical
> Labels: openjdk
> Fix For: 9.1.0.CR1
>
> Attachments: preview.png
>
>
> The editor opens the file, and its palette is displayed - the preview pane shows a 404 error.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years, 1 month
[JBoss JIRA] (JBIDE-21845) Docker connection does not work with CDK build 2016-03-09
by Hardy Ferentschik (JIRA)
[ https://issues.jboss.org/browse/JBIDE-21845?page=com.atlassian.jira.plugi... ]
Hardy Ferentschik commented on JBIDE-21845:
-------------------------------------------
I have not tested it, but it should be resolved in the CDK 2 Beta5 release. As [~mmalina] says, the issue is really with the vagrant plugin and not with the VM itself. 0.0.4 (at least) will be the version shipped with CDK 2 Beta5, so it should be resolved.
> Docker connection does not work with CDK build 2016-03-09
> ---------------------------------------------------------
>
> Key: JBIDE-21845
> URL: https://issues.jboss.org/browse/JBIDE-21845
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: cdk, upstream
> Affects Versions: 4.3.1.CR1
> Reporter: Martin Malina
> Assignee: Hardy Ferentschik
> Priority: Blocker
> Fix For: 4.3.1.CR1
>
>
> Today I tried cdk build 2016-03-09 in JBDS 9.1.0.CR1 (build from 2 days ago).
> I start cdk, the docker connection is created, but it doesn't work:
> {code}
> org.eclipse.linuxtools.docker.core.DockerException: com.spotify.docker.client.DockerException: java.util.concurrent.ExecutionException: javax.ws.rs.ProcessingException: javax.net.ssl.SSLHandshakeException: sun.security.validator.ValidatorException: PKIX path validation failed: java.security.cert.CertPathValidatorException: signature check failed
> at org.eclipse.linuxtools.internal.docker.core.DockerConnection.listImages(DockerConnection.java:787)
> at org.eclipse.linuxtools.internal.docker.core.DockerConnection.getImages(DockerConnection.java:750)
> at org.eclipse.linuxtools.internal.docker.ui.views.DockerExplorerContentProvider$5.run(DockerExplorerContentProvider.java:241)
> at org.eclipse.core.internal.jobs.Worker.run(Worker.java:55)
> Caused by: com.spotify.docker.client.DockerException: java.util.concurrent.ExecutionException: javax.ws.rs.ProcessingException: javax.net.ssl.SSLHandshakeException: sun.security.validator.ValidatorException: PKIX path validation failed: java.security.cert.CertPathValidatorException: signature check failed
> at com.spotify.docker.client.DefaultDockerClient.propagate(DefaultDockerClient.java:1141)
> at com.spotify.docker.client.DefaultDockerClient.request(DefaultDockerClient.java:1072)
> at com.spotify.docker.client.DefaultDockerClient.listImages(DefaultDockerClient.java:354)
> at org.eclipse.linuxtools.internal.docker.core.DockerConnection.listImages(DockerConnection.java:780)
> ... 3 more
> Caused by: java.util.concurrent.ExecutionException: javax.ws.rs.ProcessingException: javax.net.ssl.SSLHandshakeException: sun.security.validator.ValidatorException: PKIX path validation failed: java.security.cert.CertPathValidatorException: signature check failed
> at jersey.repackaged.com.google.common.util.concurrent.AbstractFuture$Sync.getValue(AbstractFuture.java:306)
> at jersey.repackaged.com.google.common.util.concurrent.AbstractFuture$Sync.get(AbstractFuture.java:293)
> at jersey.repackaged.com.google.common.util.concurrent.AbstractFuture.get(AbstractFuture.java:116)
> at com.spotify.docker.client.DefaultDockerClient.request(DefaultDockerClient.java:1070)
> ... 5 more
> Caused by: javax.ws.rs.ProcessingException: javax.net.ssl.SSLHandshakeException: sun.security.validator.ValidatorException: PKIX path validation failed: java.security.cert.CertPathValidatorException: signature check failed
> at org.glassfish.jersey.apache.connector.ApacheConnector.apply(ApacheConnector.java:517)
> at org.glassfish.jersey.apache.connector.ApacheConnector$1.run(ApacheConnector.java:527)
> at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511)
> at java.util.concurrent.FutureTask.run(FutureTask.java:266)
> at jersey.repackaged.com.google.common.util.concurrent.MoreExecutors$SameThreadExecutorService.execute(MoreExecutors.java:293)
> at jersey.repackaged.com.google.common.util.concurrent.AbstractListeningExecutorService.submit(AbstractListeningExecutorService.java:49)
> at jersey.repackaged.com.google.common.util.concurrent.AbstractListeningExecutorService.submit(AbstractListeningExecutorService.java:45)
> at org.glassfish.jersey.apache.connector.ApacheConnector.apply(ApacheConnector.java:523)
> at org.glassfish.jersey.client.ClientRuntime$1.run(ClientRuntime.java:169)
> at org.glassfish.jersey.internal.Errors$1.call(Errors.java:271)
> at org.glassfish.jersey.internal.Errors$1.call(Errors.java:267)
> at org.glassfish.jersey.internal.Errors.process(Errors.java:315)
> at org.glassfish.jersey.internal.Errors.process(Errors.java:297)
> at org.glassfish.jersey.internal.Errors.process(Errors.java:267)
> at org.glassfish.jersey.process.internal.RequestScope.runInScope(RequestScope.java:320)
> at org.glassfish.jersey.client.ClientRuntime$2.run(ClientRuntime.java:201)
> 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:1142)
> at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)
> at java.lang.Thread.run(Thread.java:745)
> Caused by: javax.net.ssl.SSLHandshakeException: sun.security.validator.ValidatorException: PKIX path validation failed: java.security.cert.CertPathValidatorException: signature check failed
> at sun.security.ssl.Alerts.getSSLException(Alerts.java:192)
> at sun.security.ssl.SSLSocketImpl.fatal(SSLSocketImpl.java:1949)
> at sun.security.ssl.Handshaker.fatalSE(Handshaker.java:302)
> at sun.security.ssl.Handshaker.fatalSE(Handshaker.java:296)
> at sun.security.ssl.ClientHandshaker.serverCertificate(ClientHandshaker.java:1506)
> at sun.security.ssl.ClientHandshaker.processMessage(ClientHandshaker.java:216)
> at sun.security.ssl.Handshaker.processLoop(Handshaker.java:979)
> at sun.security.ssl.Handshaker.process_record(Handshaker.java:914)
> at sun.security.ssl.SSLSocketImpl.readRecord(SSLSocketImpl.java:1062)
> at sun.security.ssl.SSLSocketImpl.performInitialHandshake(SSLSocketImpl.java:1375)
> at sun.security.ssl.SSLSocketImpl.startHandshake(SSLSocketImpl.java:1403)
> at sun.security.ssl.SSLSocketImpl.startHandshake(SSLSocketImpl.java:1387)
> at org.apache.http.conn.ssl.SSLConnectionSocketFactory.createLayeredSocket(SSLConnectionSocketFactory.java:290)
> at org.apache.http.conn.ssl.SSLConnectionSocketFactory.connectSocket(SSLConnectionSocketFactory.java:259)
> at org.apache.http.impl.conn.HttpClientConnectionOperator.connect(HttpClientConnectionOperator.java:125)
> at org.apache.http.impl.conn.PoolingHttpClientConnectionManager.connect(PoolingHttpClientConnectionManager.java:319)
> at org.apache.http.impl.execchain.MainClientExec.establishRoute(MainClientExec.java:363)
> at org.apache.http.impl.execchain.MainClientExec.execute(MainClientExec.java:219)
> at org.apache.http.impl.execchain.ProtocolExec.execute(ProtocolExec.java:195)
> at org.apache.http.impl.execchain.RetryExec.execute(RetryExec.java:86)
> at org.apache.http.impl.execchain.RedirectExec.execute(RedirectExec.java:108)
> at org.apache.http.impl.client.InternalHttpClient.doExecute(InternalHttpClient.java:184)
> at org.apache.http.impl.client.CloseableHttpClient.execute(CloseableHttpClient.java:72)
> at org.glassfish.jersey.apache.connector.ApacheConnector.apply(ApacheConnector.java:469)
> ... 20 more
> Caused by: sun.security.validator.ValidatorException: PKIX path validation failed: java.security.cert.CertPathValidatorException: signature check failed
> at sun.security.validator.PKIXValidator.doValidate(PKIXValidator.java:352)
> at sun.security.validator.PKIXValidator.engineValidate(PKIXValidator.java:260)
> at sun.security.validator.Validator.validate(Validator.java:260)
> at sun.security.ssl.X509TrustManagerImpl.validate(X509TrustManagerImpl.java:324)
> at sun.security.ssl.X509TrustManagerImpl.checkTrusted(X509TrustManagerImpl.java:229)
> at sun.security.ssl.X509TrustManagerImpl.checkServerTrusted(X509TrustManagerImpl.java:124)
> at sun.security.ssl.ClientHandshaker.serverCertificate(ClientHandshaker.java:1488)
> ... 39 more
> Caused by: java.security.cert.CertPathValidatorException: signature check failed
> at sun.security.provider.certpath.PKIXMasterCertPathValidator.validate(PKIXMasterCertPathValidator.java:135)
> at sun.security.provider.certpath.PKIXCertPathValidator.validate(PKIXCertPathValidator.java:219)
> at sun.security.provider.certpath.PKIXCertPathValidator.validate(PKIXCertPathValidator.java:140)
> at sun.security.provider.certpath.PKIXCertPathValidator.engineValidate(PKIXCertPathValidator.java:79)
> at java.security.cert.CertPathValidator.validate(CertPathValidator.java:292)
> at sun.security.validator.PKIXValidator.doValidate(PKIXValidator.java:347)
> ... 45 more
> Caused by: java.security.SignatureException: Signature does not match.
> at sun.security.x509.X509CertImpl.verify(X509CertImpl.java:424)
> at sun.security.provider.certpath.BasicChecker.verifySignature(BasicChecker.java:166)
> at sun.security.provider.certpath.BasicChecker.check(BasicChecker.java:147)
> at sun.security.provider.certpath.PKIXMasterCertPathValidator.validate(PKIXMasterCertPathValidator.java:125)
> ... 50 more
> {code}
> This looks similar to JBIDE-21733 . But in this case it doesn't work even from terminal:
> {code}
> $ eval "$(vagrant service-manager env docker)"
> $ docker ps
> An error occurred trying to connect: Get https://10.1.2.2:2376/v1.20/containers/json: x509: certificate signed by unknown authority (possibly because of "crypto/rsa: verification error" while trying to verify candidate authority certificate "example.com")
> {code}
> So yeah, this does not seem like the problem is on our site, but let's keep this JIRA for tracking anyway.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years, 1 month