[JBoss JIRA] (JBIDE-22448) Generate p2diff together when generating TP site
by Nick Boldt (JIRA)
Nick Boldt created JBIDE-22448:
----------------------------------
Summary: Generate p2diff together when generating TP site
Key: JBIDE-22448
URL: https://issues.jboss.org/browse/JBIDE-22448
Project: Tools (JBoss Tools)
Issue Type: Enhancement
Components: target-platform
Affects Versions: 4.3.1.Final
Reporter: Mickael Istria
Assignee: Mickael Istria
Fix For: 4.4.0.Alpha3
In the "multiple2repo" profile, add the necessary build steps to always generate the p2diff report.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 9 months
[JBoss JIRA] (JBIDE-22447) Explorer: Concurrent modification when scaling to a large number of pods
by Marián Labuda (JIRA)
[ https://issues.jboss.org/browse/JBIDE-22447?page=com.atlassian.jira.plugi... ]
Marián Labuda commented on JBIDE-22447:
---------------------------------------
Well, I would also recommend to do some measurements to ensure user does not use very high amount of pods for his application. E.g. I tried to scale an application for CDK to 10 pods and it crashed as far as I remember. Would it be possible to make some estimation what is reasonable amount of pods and beyond this let user inform about possible drawback/crashes/etc.?
> Explorer: Concurrent modification when scaling to a large number of pods
> ------------------------------------------------------------------------
>
> Key: JBIDE-22447
> URL: https://issues.jboss.org/browse/JBIDE-22447
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: openshift
> Affects Versions: 4.4.0.Alpha2
> Reporter: Jeff MAURY
> Labels: explorer, openshift_v3
> Fix For: 4.4.x
>
>
> When you scale a service from 1 to a large number (100), then the Openshift explorer is refreshed many times and ConcurrentModification may occur.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 9 months
[JBoss JIRA] (JBIDE-22445) Server adapter wizard: NPE when finishing
by Marián Labuda (JIRA)
[ https://issues.jboss.org/browse/JBIDE-22445?page=com.atlassian.jira.plugi... ]
Marián Labuda commented on JBIDE-22445:
---------------------------------------
[~adietish] I am able to reproduce it with devstudio Alpha3-v20160526-0626-B5438 which contains OpenShift plugin build 1318. JBIDE-21477 is already there since build 1317 therefore I should not be able to reproduce but I am still able to do it. Problem also is, that the error is not shown, at least on my FC22, as an error dialog but it is displayed only in error log. On windows there is an error dialog popped up upon hitting the Finish button.
> Server adapter wizard: NPE when finishing
> ------------------------------------------
>
> Key: JBIDE-22445
> URL: https://issues.jboss.org/browse/JBIDE-22445
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: openshift
> Affects Versions: 4.4.0.Alpha2
> Reporter: Radim Hopp
> Priority: Critical
> Labels: openshift_v3, server_adapter_wizard
> Fix For: 4.4.0.Alpha3
>
>
> I'm getting NPE when finishing New Server Wizard of Openshift 3 server adapter.
> mlabuda was also able to reproduce this bug.
> {noformat}
> java.lang.NullPointerException
> at org.eclipse.wst.server.ui.internal.wizard.TaskWizardPage.update(TaskWizardPage.java:126)
> at org.jboss.tools.openshift.internal.ui.server.ServerSettingsWizardFragment$ServerSettingsWizardPageWrapper.setPageComplete(ServerSettingsWizardFragment.java:200)
> at org.jboss.tools.openshift.internal.ui.server.ServerSettingsWizardPage.setComplete(ServerSettingsWizardPage.java:189)
> at org.jboss.tools.openshift.internal.ui.server.ServerSettingsWizardPage$1.setComplete(ServerSettingsWizardPage.java:207)
> at org.jboss.tools.openshift.internal.common.ui.databinding.FormPresenterSupport.handleComplete(FormPresenterSupport.java:243)
> at org.jboss.tools.openshift.internal.common.ui.databinding.FormPresenterSupport.handleStatusChanged(FormPresenterSupport.java:232)
> at org.jboss.tools.openshift.internal.common.ui.databinding.FormPresenterSupport.statusProviderChanged(FormPresenterSupport.java:200)
> at org.jboss.tools.openshift.internal.common.ui.databinding.FormPresenterSupport.access$2(FormPresenterSupport.java:190)
> at org.jboss.tools.openshift.internal.common.ui.databinding.FormPresenterSupport$4.handleValueChange(FormPresenterSupport.java:158)
> at org.eclipse.core.databinding.observable.value.ValueChangeEvent.dispatch(ValueChangeEvent.java:70)
> at org.eclipse.core.databinding.observable.ChangeManager.fireEvent(ChangeManager.java:117)
> at org.eclipse.core.databinding.observable.value.AbstractObservableValue.fireValueChange(AbstractObservableValue.java:82)
> at org.eclipse.core.databinding.observable.value.ComputedValue.makeDirty(ComputedValue.java:240)
> at org.eclipse.core.databinding.observable.value.ComputedValue$PrivateInterface.handleChange(ComputedValue.java:183)
> at org.eclipse.core.databinding.observable.ChangeEvent.dispatch(ChangeEvent.java:42)
> at org.eclipse.core.databinding.observable.ChangeManager.fireEvent(ChangeManager.java:117)
> at org.eclipse.core.databinding.observable.AbstractObservable.fireChange(AbstractObservable.java:71)
> at org.eclipse.core.databinding.observable.list.ObservableList.fireListChange(ObservableList.java:81)
> at org.eclipse.core.databinding.observable.list.WritableList.remove(WritableList.java:235)
> at org.eclipse.core.databinding.DataBindingContext.removeValidationStatusProvider(DataBindingContext.java:489)
> at org.eclipse.core.databinding.DataBindingContext.removeBinding(DataBindingContext.java:476)
> at org.eclipse.core.databinding.Binding.dispose(Binding.java:135)
> at org.eclipse.core.databinding.ValueBinding.dispose(ValueBinding.java:269)
> at org.eclipse.core.databinding.DataBindingContext.dispose(DataBindingContext.java:367)
> at org.jboss.tools.openshift.internal.common.ui.utils.DataBindingUtils.dispose(DataBindingUtils.java:107)
> at org.jboss.tools.openshift.internal.common.ui.wizard.AbstractOpenShiftWizardPage$1.widgetDisposed(AbstractOpenShiftWizardPage.java:79)
> at org.eclipse.swt.widgets.TypedListener.handleEvent(TypedListener.java:124)
> at org.eclipse.swt.widgets.EventTable.sendEvent(EventTable.java:84)
> at org.eclipse.swt.widgets.Display.sendEvent(Display.java:5208)
> 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:1345)
> at org.eclipse.swt.widgets.Widget.release(Widget.java:1153)
> at org.eclipse.swt.widgets.Control.release(Control.java:3989)
> at org.eclipse.swt.widgets.Widget.dispose(Widget.java:479)
> at org.eclipse.swt.widgets.Shell.dispose(Shell.java:2660)
> at org.eclipse.jface.window.Window.close(Window.java:330)
> at org.eclipse.jface.dialogs.Dialog.close(Dialog.java:989)
> at org.eclipse.jface.wizard.WizardDialog.hardClose(WizardDialog.java:853)
> at org.eclipse.jface.wizard.WizardDialog.finishPressed(WizardDialog.java:798)
> at org.eclipse.jface.wizard.WizardDialog.buttonPressed(WizardDialog.java:423)
> at org.eclipse.jface.dialogs.Dialog$2.widgetSelected(Dialog.java:618)
> 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:5208)
> at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1340)
> at org.eclipse.swt.widgets.Display.runDeferredEvents(Display.java:4542)
> at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:4132)
> at org.eclipse.jface.window.Window.runEventLoop(Window.java:818)
> at org.eclipse.jface.window.Window.open(Window.java:794)
> at org.eclipse.wst.server.ui.internal.actions.LaunchWizardAction.run(LaunchWizardAction.java:57)
> at org.eclipse.jface.action.Action.runWithEvent(Action.java:473)
> at org.eclipse.jface.action.ActionContributionItem.handleWidgetSelection(ActionContributionItem.java:565)
> at org.eclipse.jface.action.ActionContributionItem.lambda$4(ActionContributionItem.java:397)
> at org.eclipse.swt.widgets.EventTable.sendEvent(EventTable.java:84)
> at org.eclipse.swt.widgets.Display.sendEvent(Display.java:5208)
> at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1340)
> at org.eclipse.swt.widgets.Display.runDeferredEvents(Display.java:4542)
> at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:4132)
> at org.eclipse.jface.window.Window.runEventLoop(Window.java:818)
> at org.eclipse.jface.window.Window.open(Window.java:794)
> at org.eclipse.wst.server.ui.internal.actions.LaunchWizardAction.run(LaunchWizardAction.java:57)
> at org.eclipse.jface.action.Action.runWithEvent(Action.java:473)
> at org.eclipse.jface.action.ActionContributionItem.handleWidgetSelection(ActionContributionItem.java:565)
> at org.eclipse.jface.action.ActionContributionItem.lambda$4(ActionContributionItem.java:397)
> at org.eclipse.swt.widgets.EventTable.sendEvent(EventTable.java:84)
> at org.eclipse.swt.widgets.Display.sendEvent(Display.java:5208)
> at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1340)
> at org.eclipse.swt.widgets.Display.runDeferredEvents(Display.java:4542)
> at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:4132)
> at org.eclipse.jface.window.Window.runEventLoop(Window.java:818)
> at org.eclipse.jface.window.Window.open(Window.java:794)
> at org.eclipse.wst.server.ui.internal.actions.LaunchWizardAction.run(LaunchWizardAction.java:57)
> at org.eclipse.jface.action.Action.runWithEvent(Action.java:473)
> at org.eclipse.jface.action.ActionContributionItem.handleWidgetSelection(ActionContributionItem.java:565)
> at org.eclipse.jface.action.ActionContributionItem.lambda$4(ActionContributionItem.java:397)
> at org.eclipse.swt.widgets.EventTable.sendEvent(EventTable.java:84)
> at org.eclipse.swt.widgets.Display.sendEvent(Display.java:5208)
> at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1340)
> at org.eclipse.swt.widgets.Display.runDeferredEvents(Display.java:4542)
> at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:4132)
> at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine$4.run(PartRenderingEngine.java:1119)
> at org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:336)
> at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine.run(PartRenderingEngine.java:1020)
> 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:497)
> 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)
> {noformat}
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 9 months
[JBoss JIRA] (JBIDE-21121) Port Forwarding: Warning/error dialog should pop up if there is no oc binary when opening Port forwarding dialog
by Marián Labuda (JIRA)
[ https://issues.jboss.org/browse/JBIDE-21121?page=com.atlassian.jira.plugi... ]
Marián Labuda closed JBIDE-21121.
---------------------------------
Resolution: Out of Date
> Port Forwarding: Warning/error dialog should pop up if there is no oc binary when opening Port forwarding dialog
> ----------------------------------------------------------------------------------------------------------------
>
> Key: JBIDE-21121
> URL: https://issues.jboss.org/browse/JBIDE-21121
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: openshift
> Affects Versions: 4.3.1.Beta1
> Reporter: Marián Labuda
> Assignee: Dmitry Bocharov
> Labels: openshift_v3, port_forwarding_wizard
> Fix For: 4.4.0.Alpha3
>
>
> OpenShift 3 port forwarding features requires 'oc' binary to be set up in tooling. It's done in Workbench preference dialog on page OpenShift 3. If there is no 'oc' binary set and user invokes a port forwarding dialog, it is opened and even Start All button is enabled. User finds out that it is not possible to perform only when he gets an error message upon clicking on Start All button describing the problem. There could be some warning/error dialog popped up before opening a port forwarding dialog if there is no 'oc' location set in preferences.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 9 months
[JBoss JIRA] (JBIDE-21121) Port Forwarding: Warning/error dialog should pop up if there is no oc binary when opening Port forwarding dialog
by Marián Labuda (JIRA)
[ https://issues.jboss.org/browse/JBIDE-21121?page=com.atlassian.jira.plugi... ]
Marián Labuda commented on JBIDE-21121:
---------------------------------------
Yeah, it seems to be self-solved. At the moment steps leading to reproducible bug are not possible to accomplish because of fix on the OpenShift 3 preference page. I am not able to reproduce it either anymore, thus resolving and closing as out of date.
> Port Forwarding: Warning/error dialog should pop up if there is no oc binary when opening Port forwarding dialog
> ----------------------------------------------------------------------------------------------------------------
>
> Key: JBIDE-21121
> URL: https://issues.jboss.org/browse/JBIDE-21121
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: openshift
> Affects Versions: 4.3.1.Beta1
> Reporter: Marián Labuda
> Assignee: Dmitry Bocharov
> Labels: openshift_v3, port_forwarding_wizard
> Fix For: 4.4.0.Alpha3
>
>
> OpenShift 3 port forwarding features requires 'oc' binary to be set up in tooling. It's done in Workbench preference dialog on page OpenShift 3. If there is no 'oc' binary set and user invokes a port forwarding dialog, it is opened and even Start All button is enabled. User finds out that it is not possible to perform only when he gets an error message upon clicking on Start All button describing the problem. There could be some warning/error dialog popped up before opening a port forwarding dialog if there is no 'oc' location set in preferences.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 9 months
[JBoss JIRA] (JBIDE-21121) Port Forwarding: Warning/error dialog should pop up if there is no oc binary when opening Port forwarding dialog
by Dmitry Bocharov (JIRA)
[ https://issues.jboss.org/browse/JBIDE-21121?page=com.atlassian.jira.plugi... ]
Dmitry Bocharov edited comment on JBIDE-21121 at 5/26/16 10:14 AM:
-------------------------------------------------------------------
I couldn't reproduce the bug. Following the Marián's description step-by-step i get Error dialog with "The OpenShift Client ''oc' executable can not be found". And when trying to set an incorrect path to 'oc' executable the validation status is 'Value must be an existing file' and it's impossible to Apply the changes or save by Esc or closing dialog as in description.
It was fixed in https://issues.jboss.org/browse/JBIDE-20354 and https://issues.jboss.org/browse/JBIDE-21428 and
was (Author: dbocharov):
I couldn't reproduce the bug. Following the Marián's description step-by-step i get Error dialog with "The OpenShift Client ''oc' executable can not be found". And when trying to set an incorrect path to 'oc' executable the validation status is 'Value must be an existing file' and it's impossible to Apply the changes or save by Esc or closing dialog as in description.
It was fixed in:
> Port Forwarding: Warning/error dialog should pop up if there is no oc binary when opening Port forwarding dialog
> ----------------------------------------------------------------------------------------------------------------
>
> Key: JBIDE-21121
> URL: https://issues.jboss.org/browse/JBIDE-21121
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: openshift
> Affects Versions: 4.3.1.Beta1
> Reporter: Marián Labuda
> Assignee: Dmitry Bocharov
> Labels: openshift_v3, port_forwarding_wizard
> Fix For: 4.4.0.Alpha3
>
>
> OpenShift 3 port forwarding features requires 'oc' binary to be set up in tooling. It's done in Workbench preference dialog on page OpenShift 3. If there is no 'oc' binary set and user invokes a port forwarding dialog, it is opened and even Start All button is enabled. User finds out that it is not possible to perform only when he gets an error message upon clicking on Start All button describing the problem. There could be some warning/error dialog popped up before opening a port forwarding dialog if there is no 'oc' location set in preferences.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 9 months
[JBoss JIRA] (JBIDE-21121) Port Forwarding: Warning/error dialog should pop up if there is no oc binary when opening Port forwarding dialog
by Dmitry Bocharov (JIRA)
[ https://issues.jboss.org/browse/JBIDE-21121?page=com.atlassian.jira.plugi... ]
Dmitry Bocharov commented on JBIDE-21121:
-----------------------------------------
I couldn't reproduce the bug. Following the Marián's description step-by-step i get Error dialog with "The OpenShift Client ''oc' executable can not be found". And when trying to set an incorrect path to 'oc' executable the validation status is 'Value must be an existing file' and it's impossible to Apply the changes or save by Esc or closing dialog as in description.
It was fixed in:
> Port Forwarding: Warning/error dialog should pop up if there is no oc binary when opening Port forwarding dialog
> ----------------------------------------------------------------------------------------------------------------
>
> Key: JBIDE-21121
> URL: https://issues.jboss.org/browse/JBIDE-21121
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: openshift
> Affects Versions: 4.3.1.Beta1
> Reporter: Marián Labuda
> Assignee: Dmitry Bocharov
> Labels: openshift_v3, port_forwarding_wizard
> Fix For: 4.4.0.Alpha3
>
>
> OpenShift 3 port forwarding features requires 'oc' binary to be set up in tooling. It's done in Workbench preference dialog on page OpenShift 3. If there is no 'oc' binary set and user invokes a port forwarding dialog, it is opened and even Start All button is enabled. User finds out that it is not possible to perform only when he gets an error message upon clicking on Start All button describing the problem. There could be some warning/error dialog popped up before opening a port forwarding dialog if there is no 'oc' location set in preferences.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 9 months