May 2016 - jbosstools-issues - Jboss List Archives

[JBoss JIRA] (JBIDE-21708) Server Adapter:Pod deployment path is shown incorrectly in server editor

by Marián Labuda (JIRA)

[ https://issues.jboss.org/browse/JBIDE-21708?page=com.atlassian.jira.plugi... ] Marián Labuda closed JBIDE-21708. --------------------------------- Issue is out of dated. There are new JIRAs for fixing existing issues with pod deployment path. > Server Adapter:Pod deployment path is shown incorrectly in server editor > ------------------------------------------------------------------------ > > Key: JBIDE-21708 > URL: https://issues.jboss.org/browse/JBIDE-21708 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.3.1.Beta2 > Reporter: Marián Labuda > Assignee: Viacheslav Kabanovich > Labels: openshift_v3, server_adapter, server_adapter_editor > Fix For: 4.4.0.Alpha1 > > > If pod deployment path is different than the default one, it is used in new server adapter wizard. But in Server Editor is still the old one, although even in project settings is set the new one. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-21017) Blank space in a New Connection dialog

by Marián Labuda (JIRA)

[ https://issues.jboss.org/browse/JBIDE-21017?page=com.atlassian.jira.plugi... ] Marián Labuda closed JBIDE-21017. --------------------------------- Verified in Red Hat Developer Studio 10.0.0.Alpha1 B5264. > Blank space in a New Connection dialog > -------------------------------------- > > Key: JBIDE-21017 > URL: https://issues.jboss.org/browse/JBIDE-21017 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: openshift > Affects Versions: 4.3.0.CR2 > Reporter: Marián Labuda > Assignee: Andre Dietisheim > Priority: Minor > Labels: connection_wizard > Fix For: 4.4.0.Alpha1 > > Attachments: connwiz-singup-documentation-areas.png, openshift2_connection_dialog.png, openshift3_connection_dialog.png > > > There is a lot of blank space on top of OpenShift New Connection dialog. See following screenshots. Blank space is marked with red question marks. > !openshift2_connection_dialog.png! > !openshift3_connection_dialog.png! -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 11 months

1
0
0 / 0

[JBoss JIRA] (ERT-178) Search for tags of docker image with plenty of tags results to an error [EBZ#493005]

by Friendly Jira Robot (JIRA)

Friendly Jira Robot created ERT-178: --------------------------------------- Summary: Search for tags of docker image with plenty of tags results to an error [EBZ#493005] Key: ERT-178 URL: https://issues.jboss.org/browse/ERT-178 Project: Eclipse Release Train Issue Type: Task Components: Linux Tools Reporter: Friendly Jira Robot When trying to search for "php" image in Search and pull a Docker Image wizard and attempt to get its tags result to an exception. This happens right after I click on Next button in the wizard and Searching tags... job is running. I observed it happens on image with plenty of tags (but may not be the real cause). Then wizard page with image tags is shown but table where tags are supposed to be is empty. Stack trace: javax.ws.rs.ServerErrorException: HTTP 504 Gateway Time-out java.util.concurrent.ExecutionException: javax.ws.rs.ServerErrorException: HTTP 504 Gateway Time-out 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 org.eclipse.linuxtools.internal.docker.core.DockerHubRegistry.getTags(DockerHubRegistry.java:79) at org.eclipse.linuxtools.internal.docker.ui.wizards.ImageTagSelectionPage$1.run(ImageTagSelectionPage.java:97) at org.eclipse.jface.operation.ModalContext$ModalContextThread.run(ModalContext.java:119) Caused by: javax.ws.rs.ServerErrorException: HTTP 504 Gateway Time-out at org.glassfish.jersey.client.JerseyInvocation.createExceptionForFamily(JerseyInvocation.java:994) at org.glassfish.jersey.client.JerseyInvocation.convertToException(JerseyInvocation.java:975) at org.glassfish.jersey.client.JerseyInvocation.translate(JerseyInvocation.java:855) at org.glassfish.jersey.client.JerseyInvocation.access$600(JerseyInvocation.java:91) at org.glassfish.jersey.client.JerseyInvocation$6.completed(JerseyInvocation.java:815) at org.glassfish.jersey.client.ClientRuntime.processResponse(ClientRuntime.java:189) at org.glassfish.jersey.client.ClientRuntime.access$300(ClientRuntime.java:74) at org.glassfish.jersey.client.ClientRuntime$1.run(ClientRuntime.java:171) 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) -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-21746) Too much info shown in log when deploying a docker image to OpenShift

by Marián Labuda (JIRA)

[ https://issues.jboss.org/browse/JBIDE-21746?page=com.atlassian.jira.plugi... ] Marián Labuda closed JBIDE-21746. --------------------------------- Verified in Red Hat Developer Studio 10.0.0.Alpha1 B5264. > Too much info shown in log when deploying a docker image to OpenShift > --------------------------------------------------------------------- > > Key: JBIDE-21746 > URL: https://issues.jboss.org/browse/JBIDE-21746 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.3.1.CR1 > Reporter: Marián Labuda > Assignee: Viacheslav Kabanovich > Priority: Minor > Labels: openshift_v3 > Fix For: 4.4.0.Alpha1 > > > When deploying a docker image to OpenShift 3 server, there is too much logging in eclipse .log (in error log with severity info). For every created resource there is a message "Trying to create resource:" followed up by json of a resource. So for a deployed docker image it creates such info message for a new image stream, service, routing (if was checked) and deployment config. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBDS-3879) AERI - Closing the 'configure projects' dialog disables enabled projects

by Marcel Bruch (JIRA)

[ https://issues.jboss.org/browse/JBDS-3879?page=com.atlassian.jira.plugin.... ] Marcel Bruch commented on JBDS-3879: ------------------------------------ It was fixed on 2016-02-20. AFAICT this update was integrated in JBIDE some time ago. Wondering if Alpha-1 uses a different target platform than JBIDE. [~nickboldt] Can you have a look? > AERI - Closing the 'configure projects' dialog disables enabled projects > ------------------------------------------------------------------------ > > Key: JBDS-3879 > URL: https://issues.jboss.org/browse/JBDS-3879 > Project: Red Hat Developer Studio (DevStudio) > Issue Type: Bug > Components: aeri > Affects Versions: 10.0.0.Alpha1 > Environment: Version: 10.0.0.Alpha1 > Build id: Alpha1-v20160430-1625-B5264 > Build date: 20160430-1625 > Reporter: Len DiMaggio > Attachments: after.png, before.png > > > To recreate: > * Navigate to: Preferences->General->Error Reporting > * Open 'configure projects' dialog > * Enable one or more projects, click on "Enable" > * Open 'configure projects' dialog > * Close the dialog (select the 'x' at upper right) > * Open 'configure projects' dialog > * Observe that the selections are now disabled -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-21987) Improve initialization of Configure Service Ports dialog

by Marián Labuda (JIRA)

[ https://issues.jboss.org/browse/JBIDE-21987?page=com.atlassian.jira.plugi... ] Marián Labuda closed JBIDE-21987. --------------------------------- Verified in Red Hat Developer Studio 10.0.0.Alpha1 B5264. > Improve initialization of Configure Service Ports dialog > -------------------------------------------------------- > > Key: JBIDE-21987 > URL: https://issues.jboss.org/browse/JBIDE-21987 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.3.1.CR1 > Reporter: Viacheslav Kabanovich > Assignee: Viacheslav Kabanovich > Labels: deploy_docker_wizard, openshift_v3 > Fix For: 4.4.0.Alpha1 > > > When "Add..." is run on page 'Services & Routing Settings, if list of service ports is not empty, dialog is pre-filled with integers. Some errors should be fixed: > Case #1 > # ASSERT: have a project in OpenShift > # EXEC: in Explorer: choose "Deploy Docker Image..." in context menu of your project > # EXEC: in deploy docker image wizard: pick an image (ex. php), > # EXEC: confirm the 2nd wizard page ("Deployment Configuration & Scalability") and get to the 3rd wizard page > # ASSERT: no ports are defined yet > # EXEC: Create service port=65535, pod port=2000 > # EXEC: Run "Add..." second time. > Result: > Service port is filled with 65535 and causes error message. > Pod port is filled with 65536 also causing error. > Case #2 > # ASSERT: no ports are defined yet. > # EXEC: Create service port=2000, pod port=2001 > # EXEC: Run "Add..." second time. > Result: > Service port is filled with 2001 - it is ok. > Pod port is filled with 2001 causing error. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 11 months

1
0
0 / 0

[JBoss JIRA] (ERT-177) Selection and dependent functionality works wrong when a file is modified in JS Editor [EBZ#492998]

by Friendly Jira Robot (JIRA)

Friendly Jira Robot created ERT-177: --------------------------------------- Summary: Selection and dependent functionality works wrong when a file is modified in JS Editor [EBZ#492998] Key: ERT-177 URL: https://issues.jboss.org/browse/ERT-177 Project: Eclipse Release Train Issue Type: Task Components: JSDT Reporter: Friendly Jira Robot Fix For: Neon (4.6) RC1 Created attachment 261462 Selection related errors See the screenshot attached for illustration. Steps for reproduce: - Create a javascript file with a function and a call to that function. - Try to invoke content assist: FAIL: no new function appears in CA proposals - Save, close and open the file again. - Try to invoke content assist: Now the new function appears in CA proposals - Put some text (like just new lines or some statements between the function declaration and its call and select the function name in the declaration - FAIL: See wrong text regions highlighted. - Try to rename the function (with inline rename): FAIL: See the wrong places for the inline editing are highlighted. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBDS-3879) AERI - Closing the 'configure projects' dialog disables enabled projects

by Len DiMaggio (JIRA)

[ https://issues.jboss.org/browse/JBDS-3879?page=com.atlassian.jira.plugin.... ] Len DiMaggio commented on JBDS-3879: ------------------------------------ The build contains: org.eclipse.epp.logging.aeri.core_1.100.0.v20160203-1727.jar org.eclipse.epp.logging.aeri.ide_1.100.0.v20160203-1727.jar > AERI - Closing the 'configure projects' dialog disables enabled projects > ------------------------------------------------------------------------ > > Key: JBDS-3879 > URL: https://issues.jboss.org/browse/JBDS-3879 > Project: Red Hat Developer Studio (DevStudio) > Issue Type: Bug > Components: aeri > Affects Versions: 10.0.0.Alpha1 > Environment: Version: 10.0.0.Alpha1 > Build id: Alpha1-v20160430-1625-B5264 > Build date: 20160430-1625 > Reporter: Len DiMaggio > Attachments: after.png, before.png > > > To recreate: > * Navigate to: Preferences->General->Error Reporting > * Open 'configure projects' dialog > * Enable one or more projects, click on "Enable" > * Open 'configure projects' dialog > * Close the dialog (select the 'x' at upper right) > * Open 'configure projects' dialog > * Observe that the selections are now disabled -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBDS-3879) AERI - Closing the 'configure projects' dialog disables enabled projects

by Marcel Bruch (JIRA)

[ https://issues.jboss.org/browse/JBDS-3879?page=com.atlassian.jira.plugin.... ] Marcel Bruch commented on JBDS-3879: ------------------------------------ Which AERI version does Alpha1-v20160430-1625-B5264 contain? Or: Can you please share the download link to that version? I'm not yet familiar where I can find these versions. This should have been fixed a while ago [1] [1] https://git.eclipse.org/c/epp/org.eclipse.epp.logging.git/commit/?id=540c... > AERI - Closing the 'configure projects' dialog disables enabled projects > ------------------------------------------------------------------------ > > Key: JBDS-3879 > URL: https://issues.jboss.org/browse/JBDS-3879 > Project: Red Hat Developer Studio (DevStudio) > Issue Type: Bug > Components: aeri > Affects Versions: 10.0.0.Alpha1 > Environment: Version: 10.0.0.Alpha1 > Build id: Alpha1-v20160430-1625-B5264 > Build date: 20160430-1625 > Reporter: Len DiMaggio > Attachments: after.png, before.png > > > To recreate: > * Navigate to: Preferences->General->Error Reporting > * Open 'configure projects' dialog > * Enable one or more projects, click on "Enable" > * Open 'configure projects' dialog > * Close the dialog (select the 'x' at upper right) > * Open 'configure projects' dialog > * Observe that the selections are now disabled -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-21779) Environment variables validation in deploy docker image wizard is not correct/consistent

by Marián Labuda (JIRA)

[ https://issues.jboss.org/browse/JBIDE-21779?page=com.atlassian.jira.plugi... ] Marián Labuda closed JBIDE-21779. --------------------------------- Verified in Red Hat Developer Studio 10.0.0.Alpha1 B5264. > Environment variables validation in deploy docker image wizard is not correct/consistent > ---------------------------------------------------------------------------------------- > > Key: JBIDE-21779 > URL: https://issues.jboss.org/browse/JBIDE-21779 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.3.1.CR1 > Reporter: Marián Labuda > Assignee: Viacheslav Kabanovich > Labels: docker, openshift_v3 > Fix For: 4.4.0.Alpha1 > > Attachments: env_var_validation.png, invalid_env_var_value.png > > > On 2nd page of Deploy Docker Image wizard is page containing environment variable. Dialog to create a new environment variable has a validation message but it is not correct, or at least validation message content does not fit reality. See following screenshots: > First one is when entered invalid environment variable name. Notice message contains info about invalid value, not name, although it is name what is not valid. > !env_var_validation.png! > Second screeshoot displays so-called invalid value (regarding to validation message in first screenshot), but there is no validation error. > !invalid_env_var_value.png! -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 11 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 May 2016