[JBoss JIRA] (JBIDE-22243) Properties: "Refresh" has no effect
by Marián Labuda (JIRA)
[ https://issues.jboss.org/browse/JBIDE-22243?page=com.atlassian.jira.plugi... ]
Marián Labuda edited comment on JBIDE-22243 at 8/15/16 8:18 AM:
----------------------------------------------------------------
Well, partially yeah. Click on a table item update the content shown for the item in Properties view. But right mouse click on a item and select Refresh do nothing. There is a job Loading OpenShift information, but the content (e.g. replicas) stay same until I do left mouse click.
[~fbricon] [~adietish] are you satisfied with having refresh by click on an item in properties view? Becaus Refresh context menu is not still working. I am inclined to reopen this issue, because this JIRA is really about Refresh context menu item.
was (Author: mlabuda):
Well, partially yeah. Click on a table item update the content shown for the item in Properties view. But right mouse click on a item and select Refresh do nothing. There is a job Loading OpenShift information, but the content (e.g. replicas) stay same until I do left mouse click.
> Properties: "Refresh" has no effect
> -----------------------------------
>
> Key: JBIDE-22243
> URL: https://issues.jboss.org/browse/JBIDE-22243
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: openshift
> Affects Versions: 4.4.0.Alpha1
> Reporter: Andre Dietisheim
> Assignee: Jeff Cantrill
> Fix For: 4.4.1.AM3
>
> Attachments: refreshing-wont-help.ogv
>
>
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 7 months
[JBoss JIRA] (JBIDE-22860) Application Wizard: Improve layout for templates
by Andre Dietisheim (JIRA)
[ https://issues.jboss.org/browse/JBIDE-22860?page=com.atlassian.jira.plugi... ]
Andre Dietisheim updated JBIDE-22860:
-------------------------------------
Fix Version/s: 4.4.1.Final
> Application Wizard: Improve layout for templates
> ------------------------------------------------
>
> Key: JBIDE-22860
> URL: https://issues.jboss.org/browse/JBIDE-22860
> Project: Tools (JBoss Tools)
> Issue Type: Enhancement
> Components: openshift
> Affects Versions: 4.4.1.AM2
> Reporter: Marián Labuda
> Priority: Minor
> Labels: application_wizard, openshift_v3
> Fix For: 4.4.1.Final
>
>
> In the New OpenShift Application wizard we have 2 tabs for a decision on what should a new application be based. One for server-template-based application (either from templates or builder images) and one for "Local template". Problem with local template is that it supports usage of URL templates - I can provide an URL of a template. This is not really local template. I think we should rename "Local template" tab to "Custom template" or something what would suggest usage of URLs as well as templates from local file system.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 7 months
[JBoss JIRA] (JBIDE-22851) Deploy Docker Wizard: Unhandled event loop exception in Search dialog
by Marián Labuda (JIRA)
[ https://issues.jboss.org/browse/JBIDE-22851?page=com.atlassian.jira.plugi... ]
Marián Labuda closed JBIDE-22851.
---------------------------------
Verified in DevStudio 10.1.0.AM3 build ID AM3-v20160812-1839-B5760.
> Deploy Docker Wizard: Unhandled event loop exception in Search dialog
> ---------------------------------------------------------------------
>
> Key: JBIDE-22851
> URL: https://issues.jboss.org/browse/JBIDE-22851
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: openshift, upstream
> Affects Versions: 4.4.1.AM2
> Environment: Fedora 24, GTK 3
> Reporter: Marián Labuda
> Assignee: Andre Dietisheim
> Priority: Critical
> Labels: deploy_docker_wizard, openshift_v3, upstream
> Fix For: 4.4.1.AM3
>
>
> In Deploy Image to OpenShift wizard opened via context menu item Deploy Docker Image of a project in OpenShift Explorer view, there is a Search button which opens a Search wizard to search for images on docker hub.
> At the moment, when I search any image, table showing images is empty and there is Unhandled Event Loop Exception with following stack trace
> {code}
> org.eclipse.swt.SWTException: Graphic is disposed
> at org.eclipse.swt.SWT.error(SWT.java:4533)
> at org.eclipse.swt.SWT.error(SWT.java:4448)
> at org.eclipse.swt.SWT.error(SWT.java:4419)
> at org.eclipse.swt.graphics.Image.getBounds(Image.java:1321)
> at org.eclipse.linuxtools.internal.docker.ui.wizards.ImageSearchPage$IconColumnLabelProvider.measure(ImageSearchPage.java:436)
> at org.eclipse.jface.viewers.OwnerDrawLabelProvider$OwnerDrawListener.handleEvent(OwnerDrawLabelProvider.java:56)
> at org.eclipse.swt.widgets.EventTable.sendEvent(EventTable.java:84)
> at org.eclipse.swt.widgets.Display.sendEvent(Display.java:5219)
> at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1340)
> at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1366)
> at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1349)
> at org.eclipse.swt.widgets.Table.sendMeasureEvent(Table.java:2653)
> at org.eclipse.swt.widgets.Table.rendererGetPreferredWidthProc(Table.java:2673)
> at org.eclipse.swt.widgets.Display.rendererGetPreferredWidthProc(Display.java:1398)
> at org.eclipse.swt.internal.gtk.OS._gtk_cell_renderer_get_preferred_size(Native Method)
> at org.eclipse.swt.internal.gtk.OS.gtk_cell_renderer_get_preferred_size(OS.java:6838)
> at org.eclipse.swt.widgets.Widget.gtk_cell_renderer_get_preferred_size(Widget.java:2076)
> at org.eclipse.swt.widgets.Table.rendererRender(Table.java:2772)
> at org.eclipse.swt.widgets.Table.rendererRenderProc(Table.java:2690)
> at org.eclipse.swt.widgets.Display.rendererRenderProc(Display.java:1412)
> at org.eclipse.swt.internal.gtk.OS._gtk_main_do_event(Native Method)
> at org.eclipse.swt.internal.gtk.OS.gtk_main_do_event(OS.java:9545)
> at org.eclipse.swt.widgets.Display.eventProc(Display.java:1275)
> at org.eclipse.swt.internal.gtk.OS._g_main_context_iteration(Native Method)
> at org.eclipse.swt.internal.gtk.OS.g_main_context_iteration(OS.java:2495)
> at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:4141)
> at org.eclipse.jface.window.Window.runEventLoop(Window.java:818)
> at org.eclipse.jface.window.Window.open(Window.java:794)
> at org.jboss.tools.openshift.internal.ui.wizard.deployimage.DeployImagePage$3.widgetSelected(DeployImagePage.java:251)
> at org.eclipse.swt.widgets.TypedListener.handleEvent(TypedListener.java:249)
> at org.eclipse.swt.widgets.EventTable.sendEvent(EventTable.java:84)
> at org.eclipse.swt.widgets.Display.sendEvent(Display.java:5219)
> at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1340)
> at org.eclipse.swt.widgets.Display.runDeferredEvents(Display.java:4553)
> at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:4143)
> at org.eclipse.jface.window.Window.runEventLoop(Window.java:818)
> at org.eclipse.jface.window.Window.open(Window.java:794)
> at org.jboss.tools.common.ui.WizardUtils.openWizardDialog(WizardUtils.java:257)
> at org.jboss.tools.openshift.internal.ui.handler.DeployImageHandler$2$1.run(DeployImageHandler.java:94)
> at org.eclipse.swt.widgets.RunnableLock.run(RunnableLock.java:35)
> at org.eclipse.swt.widgets.Synchronizer.runAsyncMessages(Synchronizer.java:182)
> at org.eclipse.swt.widgets.Display.runAsyncMessages(Display.java:4528)
> at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:4146)
> at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine$4.run(PartRenderingEngine.java:1121)
> at org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:336)
> at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine.run(PartRenderingEngine.java:1022)
> at org.eclipse.e4.ui.internal.workbench.E4Workbench.createAndRunUI(E4Workbench.java:150)
> at org.eclipse.ui.internal.Workbench$5.run(Workbench.java:687)
> at org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:336)
> at org.eclipse.ui.internal.Workbench.createAndRunWorkbench(Workbench.java:604)
> at org.eclipse.ui.PlatformUI.createAndRunWorkbench(PlatformUI.java:148)
> at org.eclipse.ui.internal.ide.application.IDEApplication.start(IDEApplication.java:138)
> at org.eclipse.equinox.internal.app.EclipseAppHandle.run(EclipseAppHandle.java:196)
> at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.runApplication(EclipseAppLauncher.java:134)
> at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.start(EclipseAppLauncher.java:104)
> at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:388)
> at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:243)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
> at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> at java.lang.reflect.Method.invoke(Method.java:498)
> at org.eclipse.equinox.launcher.Main.invokeFramework(Main.java:673)
> at org.eclipse.equinox.launcher.Main.basicRun(Main.java:610)
> at org.eclipse.equinox.launcher.Main.run(Main.java:1519)
> at org.eclipse.equinox.launcher.Main.main(Main.java:1492)
> {code}
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 7 months
[JBoss JIRA] (JBIDE-22695) Environment Variables of application deployment should have different workflow
by Andre Dietisheim (JIRA)
[ https://issues.jboss.org/browse/JBIDE-22695?page=com.atlassian.jira.plugi... ]
Andre Dietisheim updated JBIDE-22695:
-------------------------------------
Fix Version/s: 4.4.x
> Environment Variables of application deployment should have different workflow
> ------------------------------------------------------------------------------
>
> Key: JBIDE-22695
> URL: https://issues.jboss.org/browse/JBIDE-22695
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: openshift
> Affects Versions: 4.4.1.AM1
> Reporter: Marián Labuda
> Priority: Critical
> Labels: env_var_wizard, openshift_v3
> Fix For: 4.4.x
>
>
> Reset All button in Environment Var wizard dialog should get application to default state. At the moment it reset environment variables in the table just to the values at the point of opening the wizard. If I would delete some environment variables and confirm changes, but I would find out I broke something and I would like to rollback it to original state, I would try to reset it with Reset All button. But it won't work for me. This is causing the more serious issue:
> Because we edit same deployment configuration and start deployments from it and in the same time we set number of replicas in other deployment configs to zero. So we don't have the original deployment config and thus we cannot rollback easily (well there is a way but nasty one - edit replication controller, copy and paste environment variables to the deployment config, save it and deploy latest).
> There are 2 options:
> a) Create a new deployment configuration for a new (modified) set of environment variables and create a new replication controller (deployment) from this deployment configuration. There is one con - it can lead to many deployment configurations and replication controllers (for each deployment configuration there would be one replication controller).
> b) Just edit current replication controller (deployment) of an application or create a new one from an existing but with modified env. vars and with correct amount of replicas and set replicas in the previous to 0. And then let respin pods with correct setup. One of those approaches (create/edit RC) would be, I think, more satisfying.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 7 months
[JBoss JIRA] (JBIDE-22695) Environment Variables of application deployment should have different workflow
by Andre Dietisheim (JIRA)
[ https://issues.jboss.org/browse/JBIDE-22695?page=com.atlassian.jira.plugi... ]
Andre Dietisheim updated JBIDE-22695:
-------------------------------------
Labels: env_var_wizard openshift_v3 (was: openshift_v3)
> Environment Variables of application deployment should have different workflow
> ------------------------------------------------------------------------------
>
> Key: JBIDE-22695
> URL: https://issues.jboss.org/browse/JBIDE-22695
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: openshift
> Affects Versions: 4.4.1.AM1
> Reporter: Marián Labuda
> Priority: Critical
> Labels: env_var_wizard, openshift_v3
> Fix For: 4.4.x
>
>
> Reset All button in Environment Var wizard dialog should get application to default state. At the moment it reset environment variables in the table just to the values at the point of opening the wizard. If I would delete some environment variables and confirm changes, but I would find out I broke something and I would like to rollback it to original state, I would try to reset it with Reset All button. But it won't work for me. This is causing the more serious issue:
> Because we edit same deployment configuration and start deployments from it and in the same time we set number of replicas in other deployment configs to zero. So we don't have the original deployment config and thus we cannot rollback easily (well there is a way but nasty one - edit replication controller, copy and paste environment variables to the deployment config, save it and deploy latest).
> There are 2 options:
> a) Create a new deployment configuration for a new (modified) set of environment variables and create a new replication controller (deployment) from this deployment configuration. There is one con - it can lead to many deployment configurations and replication controllers (for each deployment configuration there would be one replication controller).
> b) Just edit current replication controller (deployment) of an application or create a new one from an existing but with modified env. vars and with correct amount of replicas and set replicas in the previous to 0. And then let respin pods with correct setup. One of those approaches (create/edit RC) would be, I think, more satisfying.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 7 months
[JBoss JIRA] (JBIDE-22853) Missing connection error shows sometimes on existing connection
by Andre Dietisheim (JIRA)
[ https://issues.jboss.org/browse/JBIDE-22853?page=com.atlassian.jira.plugi... ]
Andre Dietisheim commented on JBIDE-22853:
------------------------------------------
I cannot reproduce this unfortunately. Do you have several connections, does it even matter?
> Missing connection error shows sometimes on existing connection
> ---------------------------------------------------------------
>
> Key: JBIDE-22853
> URL: https://issues.jboss.org/browse/JBIDE-22853
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: openshift
> Affects Versions: 4.4.1.AM2
> Reporter: Marián Labuda
> Labels: connection, openshift_v3
> Fix For: 4.4.1.Final
>
>
> Sometimes when I am working with console.engint.openshift.com instance where I use OAuth authentication, I get following error in error log with no stack trace when trying to create a project or application on a connection
> {code}
> Could not create project, missing connection.
> {code}
> Then when I open Edit Connection wizard via context menu of the connection, there is an error in header of the wizard "Connection for the server with this token already exists."
> Not sure what precisely it is causing and how to reproduce it with success rate 100 %.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 7 months
[JBoss JIRA] (JBIDE-22853) Missing connection error shows sometimes on existing connection
by Andre Dietisheim (JIRA)
[ https://issues.jboss.org/browse/JBIDE-22853?page=com.atlassian.jira.plugi... ]
Andre Dietisheim updated JBIDE-22853:
-------------------------------------
Fix Version/s: 4.4.1.Final
> Missing connection error shows sometimes on existing connection
> ---------------------------------------------------------------
>
> Key: JBIDE-22853
> URL: https://issues.jboss.org/browse/JBIDE-22853
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: openshift
> Affects Versions: 4.4.1.AM2
> Reporter: Marián Labuda
> Labels: connection, openshift_v3
> Fix For: 4.4.1.Final
>
>
> Sometimes when I am working with console.engint.openshift.com instance where I use OAuth authentication, I get following error in error log with no stack trace when trying to create a project or application on a connection
> {code}
> Could not create project, missing connection.
> {code}
> Then when I open Edit Connection wizard via context menu of the connection, there is an error in header of the wizard "Connection for the server with this token already exists."
> Not sure what precisely it is causing and how to reproduce it with success rate 100 %.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 7 months